Web services and SaaS
A service people return to, not a site for one visit
A web application is needed when a person has a reason to come back: an order, a task, a subscription, a report, an object. I build client accounts, SaaS, internal panels, and online services, from a narrow MVP to a system with roles and payment.
What it takes on
- 01
Give the client an account
Order status, documents, inquiries, and payment stop living in a messenger.
- 02
Test the product with an MVP
One scenario launches, one you can already charge for, or seat users in.
- 03
Build a panel for the team
Staff work through a queue, instead of searching the chat for the current state.
- 04
Separate the organizations
Each company has its own users, data, and permissions, when this is a SaaS.
Who it is for
Founders of a service
There is a hypothesis, and you need a product you can show to clients, not a presentation.
Companies with a client account
Clients already write “where is my status?” It is time to take that question out of email.
Operations teams
You need an internal panel: a queue, assignments, and control, without a public storefront.
If a person comes once, reads about the service, and leaves a phone number, that is a website. A service with nothing to do after registration only looks like a product.
What can be built
Client account
State, history, documents, and the client's own actions.
SaaS
Registration, organizations, roles, and the limits of a plan.
Online service
A useful action in the browser, not only content.
Platform
Several types of users, and accounts that are linked.
Control panel
A task queue, filters, a card, and bulk states.
Complex interaction
Builders, calculations, boards, and dense working screens.
How it looks in practice
- 01
You need to test whether people will pay
The MVP includes registration, one useful scenario, and a way to take a payment or a request. An admin area “for later” does not block the launch.
- 02
Clients ask for the status in chat
The account shows which step the order is on, and leaves the manager only the exceptions. Correspondence stays for live questions.
- 03
The team needs its own panel
Tasks, shifts, or moderation do not fit in a spreadsheet. The panel follows an employee's shift: what to open in the morning, and what to close in the evening.
How development goes
- 01
The scenario that has value
The one action without which there is no product.
- 02
Roles and data
Who signs in, what they see, and what counts as a record.
- 03
The contents of the MVP
A list of what we deliberately do not build in the first version.
- 04
Workplace interfaces
The client account and the team panel.
- 05
Build
Sign-in, states, errors, and empty screens.
- 06
Launch
An environment, access, a way to see errors, and handover of the code.
Technologies
- TypeScript
- React
- Next.js
- PostgreSQL
- Authentication and roles
- REST API
You receive an application with the main scenario, the source code, a description of the roles, and a way to deploy it again.
Demonstrations on this topic
Request console
A workplace where a request is not lost between email and a spreadsheet.
Request board
A request lives on the board, not in the correspondence between the measurer and the manager.
Order account
The client needs the status of the order, not the company's whole board.
Slice
An independent concept for analytics. Revenue, cost, and profit are summed from sample rows.
Stall
An independent shop concept: catalog, product, cart, and a sample order with no payment.
Slot
An independent booking concept. A service, a person, and a slot that cannot be taken twice.
Route
An independent delivery concept: statuses, couriers, and an event log. The coordinates are a sample.
Hire
An independent recruiting concept: cards, stages, and a note.
Class
An independent learning concept: lessons, progress, an assignment, and a teacher view.
How to commission it
A project with a clear scope
We agree what goes into the next batch, and we hand over that scope, not an endless list of ideas.
MVP
We build one scenario you can already work in, or use to test demand. The rest is not thrown away. It goes into the next batch.
Support
After launch, there is someone to give a bug, a question, or a new branch of the process.
Questions
What do you mean by an MVP?
It is not a rough sketch. It is a short product: one scenario runs from start to finish, errors do not stay silent, and everything else is written into the next batch. There is more in the piece on what an MVP contains.
Can we start without payment and subscriptions?
Yes. If the hypothesis is not about money yet, the first version includes a useful action and a way to collect feedback. Billing should not delay a test of demand.
How is a service different from a CRM?
A CRM runs the company's process. A service is more often given to an outside user, or used as the product itself. The two can meet: a client account plus internal records. Then it is one project with two workplaces.
Does the code stay with us?
Yes. The repository and the way to build it are handed over. You are not tied to my laptop in order to release the next version.
Can a mobile app come later?
Yes, if the scenario justifies it. At the start, an account in the browser is often enough. The server logic does not have to be thrown away.