You're the system
holding it all together.
That's the problem.

Four functions: operational dashboard with role-based access (revenue, pipeline, team capacity, client health), one workflow automation of your choice, AI assistant, notification centre. Plus the infrastructure (hosting, authentication, database) and 2 to 3 data connections agreed in scoping (typically finance, calendar, email, and one source specific to your business). Your knowledge wiki is initialised here too. The Day 7 MVP is the operational dashboard live on your data; the rest is built out by week 6.

A Function adds something new: a new data connection, a new interface, a new AI workflow, a new automation. An Enhancement is a minor addition to something already built: filtering, CSV export, UI tweaks, adding a column. Enhancements are included before the build starts and bundled into the scope document. Once the scope is approved, it's frozen — new requests go to the next Function Cycle. Every request classified within 24 hours.

Ben builds it. No subcontractors, no outsourcing, no handoffs. You work directly with the same person from discovery call to deployment.

If Ben misses any committed milestone, you get SGD 200 back per day late. Written into the service agreement, not a marketing claim. Credit applies against your next invoice, or is refunded directly if there's no future invoice. One caveat: the 6-week SLA depends on fast feedback from your side — typically within 48 hours. We move fast; we need you to as well. The 6-week build is short because momentum matters: every blocked decision compounds. If feedback consistently takes longer, the SLA pauses for that period (the days don't count against the deadline). We'll always flag this in writing before the timer pauses.

Yes. After scope: 95% back. After MVP: 70% back. Cancel after any Function Cycle: no penalty. All code delivered is yours regardless. No lock-in.

Completely. Every line of code, every database, the infrastructure, the SOPs, the knowledge wiki — everything becomes your sole property on delivery. Ben retains no license or rights. If we ever part ways, the system continues to work as intended.

Every SOP, role, responsibility, decision, and rule that shapes how your business runs. Cross-linked. Searchable from inside the AI assistant. Maintained as part of every Function Cycle. It's the difference between a system that works for you and a system you actually own. If we ever part ways, the wiki and the system continue to work as intended.

We usually have three sessions before any code is written. Session 1: a free 30-minute discovery call to qualify both sides. Session 2: a 1-hour audit of your current workflows, tools, and data. Session 3: if we decide to work together, the 48-hour scoping period starts. We meet to confirm scope, then the day-7 MVP build kicks off. You can cancel at any point: 95% back after scoping, 70% back after MVP. Code delivered to that point is yours regardless.

Good fit: a service business of 10 to 35 people, a founder who can describe what's broken, data that already exists but isn't centralised. Poor fit: a business that hasn't started, needs a consumer product, or can't give 48-hour feedback during the build.