The business OS behind the studio.
A private, local-first workspace that takes an enquiry from first reply to signed scope, invoice and portal login. Built and run by one developer, for one developer.
Not a product for sale. No client names, logos, testimonials or revenue figures appear on this page: there are none with a source I can show. What follows is the problem, the system, the stack and the limits.
- Role
- Product design + full-stack, solo
- Stack
- Next.js 16 · MongoDB · Redis · pm2
- Shape
- Local-first; Vercel view layer
- First commit
- 2026-03-10
01 · The problem
Selling a service solo means four jobs at once.
To sell a website as one person, you are the sales team, the project manager, the accountant and the person doing the work. Off-the-shelf CRMs assume a team: seats, pipelines and a monthly bill for features that never connect the one thing that matters, an enquiry becoming a paid invoice.
So the work leaks into spreadsheets, inboxes and memory. A client is asked the same question twice. A follow-up is missed between two inboxes. An invoice is paid but the project still says outstanding. The leaks are not dramatic. They are just expensive, one missed follow-up at a time.
The toolkit exists to close that loop in one workspace: enquire, scope, approve, quote, contract, invoice, reconcile, deliver and keep the client in the picture.
02 · What it does
Eight jobs, one workspace.
This is not a dashboard skin over a spreadsheet. Each block below is a working surface with a rule behind it.
- 01
Enquiry and intake
One inbound enquiry is added by hand: the person, what they need and where the conversation stands. The rest of the workspace is built around that record.
- 02
Proposals and contracts
A scope becomes a written proposal with line-item pricing, then a contract both parties sign. Revisions are versioned, and a signature records who signed, when, and from where. Nothing is agreed verbally and reconstructed later.
- 03
Projects and delivery
Every accepted proposal becomes a project with milestones, tasks, time entries and a delivery state. The tracker is the one place that answers where the work stands, for the client and for me.
- 04
Approvals
One queue reviews every proposal and contract before it reaches a client. The owner approves, and an edit after queueing sends the item back for a fresh read. A document never leaves the workspace without a human decision.
- 05
Invoices and UPI
Line-item invoices, PDFs and tokenized share links. The pay page shows a UPI QR only on INR invoices and bank details for every currency. The client claims a transfer, the owner confirms it, and only then does the invoice flip to paid.
- 06
Client portal
Login, projects, invoices, files, messages and approvals for the client, with a token separate from the admin session. Every query is scoped through that client's project filter; a token proves identity, never ownership.
- 07
Mobile companion
A read-mostly PWA for the morning: Today, Work, Clients, Approvals and Money. Approvals call the same decision function as the web, and Web Push carries the events that matter. No native build, no store.
- 08
Practice room for calls
A local rehearsal against six fictional personas, or one built from an existing project record. The debrief separates measured talk ratio, questions, fillers and next-step from an advisory AI read; the two are never blended into one score.
03 · Architecture
The laptop is the record. Failures are loud.
The laptop is the record; the cloud is a view. The local MongoDB is the source of truth. A custom Node server runs the Next.js app with Socket.IO, the cron scheduler and the admin bootstrap under pm2. Vercel serves a view layer over an Atlas copy.
01 · Surfaces
- Desktop admin shell
- Phone PWA, read-mostly
- Client portal and public links
02 · Application
- Next.js 16 App Router
- Handlers: CRM, proposals, money, portal, mobile
- Edge proxy: allowlist, rate limit, CSP
03 · State and runtime
- MongoDB, local SSOT and Atlas view
- Redis: cache, queue, Socket.IO adapter
- pm2: Next, Socket.IO, cron scheduler
Request path
browser → proxy → route handler → Mongoose → Mongo / Redis → response
- Process model
- No Docker
- Cron split
- Seven on Vercel, the rest local
- Single executor
- One cron lock, no duplicate runs
04 · The stack
Boring where it counts.
The choices favour a system one person can operate at 2 a.m.: one framework, one database, one cache, one process manager and a small number of well-understood libraries.
- Framework
- Next.js 16 App Router, React 19, TypeScript.
- Data
- MongoDB with Mongoose 9. The laptop database is the source of truth; Atlas is the deployed copy.
- Cache, queue, realtime
- Redis (ioredis) for cache and queue, Socket.IO with the Redis adapter, SSE for the activity stream.
- Runtime
- A custom Node server under pm2: Next.js, Socket.IO, the local cron scheduler and admin bootstrap. No Docker.
- Deploy
- Vercel serves a view layer and seven production crons over Atlas. Client links go out only after a local-to-Atlas sync.
- Auth
- JWT admin sessions (jose), scrypt password hashing, TOTP 2FA, plus separate portal and mobile tokens.
- Documents
- jsPDF for invoices and proposals, sharp for images, tokenized public pages for proposals, contracts and files.
- Practice engine
- A loopback Python service with local speech-to-text, text-to-speech and an 8B model. Call audio never leaves the machine.
05 · What it demonstrates
Full-stack product ownership, not a landing page.
A system that holds a money path has to survive contact with identity, permissions, retries and a client on the other side of the screen. The interesting work is in the seams.
One owner, every layer
Schema, API, UI, auth, money, deploy and the client-facing surface are one person's decisions. Nothing is lost between a designer and a dev team, because there is no handoff.
Review as architecture
Every proposal and contract leaves through one queue. The owner reads it, and the same decision path runs on the web and on the phone. No automation can mark a document approved.
Money as a state machine
The invoice total is the only settlement authority. A client's claim is metadata; the status flips conditionally on the owner's confirmation. Derived money fields are never client-settable.
06 · How it is verified
Measured, including the awkward parts.
This is engineering evidence, not commercial validation. The numbers below are dated and reproducible; the failures are printed with the passes.
- Four static gates before every commit: typecheck, lint, knip and circular-dependency checks.
- A money-path smoke test on a scratch database: enquiry → proposal → invoice → pay page → claim → reconcile → paid, plus a contract signed by both parties. Dated runs: 25/26 (2026-10-16, one step needed a MongoDB transaction on a standalone mongod), 24/26 (2026-10-19, both failures environmental: loopback link guard, unset bank details) and 27/27 (2026-10-23, the current run: the whole path passed).
- A portal scope probe asserts 49 access rules, and a mobile drift harness requires the phone's read counts to equal the web's.
- The practice room's acceptance run sends real synthesised audio through speech-to-text, with a measured median of about 1.0 s to first reply audio (2026-11-04).
- Migrations ship with dry-run, status and rollback. Backups ship with a restore verification, because a backup nobody restored is a hope.
07 · The honest boundary
What this does not prove.
- No client names, logos, testimonials or revenue figures appear here, because there are none with a source I can show. As of 2026-11-05 the toolkit has no client accounts and no paid invoices. It is the system I built to run this practice from the first enquiry, not a record of clients won.
- The money path is proven on a scratch database, not by a paid production invoice. The engineering is tested; the market is not.
- The practice room is rehearsal. The built-in personas are fictional, and a persona generated from an existing project record never sends, tags or writes back to that client.
- The app is login-gated. A screenshot would either expose a real client's data or invent one, so this page documents the architecture instead.
- It is one operator's tool for one practice: not multi-tenant, not a SaaS, not for sale.
08 · The same ownership, applied to your product
You do not need a team to have the whole path owned.
If you need someone who can design the schema, build the interface, wire the money and stay through the launch, that is the work. The same standard applies to a client system: fixed written scope before code, and a measured handover.
This case study documents my own system, not a client engagement. The concept builds under /work carry their own dated measurements and no client affiliation.