No vague proposals. No briefing chains. The sequence below is what happens, in the order it happens, with the dates committed in writing. SGD 200 back per day late on any missed milestone.
Read it like a contract. That is roughly what it is.
Every engagement runs the same path. The 30-minute discovery call and 1-hour workflow audit are free. Pricing kicks in once you commit to proceed. From that point on, refund tiers protect you at every stage — 95% back after scope, 70% after MVP.
A 30-minute conversation. We talk about your business, the bottleneck you are hitting, and whether what we build is the right answer. No pitch, no proposal. If we are not a fit, you hear it on the call and we move on. If both sides see a fit, we move to the audit.
About an hour. We go through your tools, your data, your manual processes — together. The audit is the basis for the scope: it identifies which workflow becomes the automation function, which data sources feed the dashboard, where the friction actually lives. If both sides want to proceed after this, you commit — and the scope work begins.
Once you commit, the scope work starts. Within 48 hours you receive a complete written scope: deliverables, timeline, cost, assumptions, every Function and Enhancement bundled in. No vague statements of work. We meet to agree. Cancel at this point: 95% back.
Seven days after scope approval, your operational dashboard is live on real data — revenue, pipeline, team capacity, client health. Not a mockup. Not a demo. Your actual data, in your actual environment, behind authentication. We run two iteration rounds with you during this phase — you test, we tune. Cancel after MVP: 70% back.
Six weeks from scope approval, all four functions are complete and deployable: operational dashboard, workflow automation, AI assistant, notification centre. Plus the infrastructure (hosting, authentication, database) and the data connections agreed in scope. If we miss any committed milestone, you get SGD 200 back per day late. Written into the agreement.
Code, infrastructure, SOPs, and the knowledge wiki — every artefact transferred to you. We retain no licenses, no rights. From here, two paths and you can switch between them: Function Cycles (SGD 2,400 each) add new capabilities one at a time, on the same 48hr/Day-7/6-week cadence. Maintain Mode keeps the build supported — hosting, updates, AI refresh, async support. Open a Function Cycle whenever a new need lands.
Every Foundation Build delivers the same four functions, built around your specific data and workflows. Same architecture, same commitments — adapted to what your business actually does.
Revenue, pipeline, team capacity, client health — the whole business in one view. Founder sees everything; team leads see their scope. Role-based access from day one. This is what goes live on Day 7 as the MVP.
One workflow chosen with you in scoping. Compliance approval chains, data-to-PDF reports, intake forms, manual review pipelines. The workflow eating the most of your team's hours, gone — and the saved hours redirected.
Ask in plain English. "Who's overdue?" "What's pipeline this month?" "Which clients haven't been contacted in 30 days?" Answers come from your live data, in seconds, with citations to the records they came from.
The system tells you when something needs attention. Thresholds you set: revenue dips, client risk, capacity flags, deadlines approaching. No noise. Only the signals you asked it to surface.
Hosting, authentication, and the database. 2 to 3 data connections agreed in scoping (typically finance, calendar, email, and one source specific to your business). The knowledge wiki initialised here too — every SOP, role, decision, and rule that shapes how your business runs, cross-linked and searchable from inside the AI assistant.
Foundation done. From here, you keep building or you settle in. Most clients run a few cycles, then move to maintain — and open a cycle whenever something new surfaces.
One capability per cycle. Built the same way, every time. Add as many as you need; stop the moment you don't.
Foundation built. No new functions in flight. We keep the system tuned and supported.
These aren't aspirations. Every commitment below is in the service agreement, with the dollar figures and refund percentages spelled out.
After scope: 95% back. After MVP: 70% back. Cancel after any Function Cycle: no penalty. Work delivered to that point is yours regardless. There is nothing to renew, nothing to escape.
Enhancements are bundled into scope before the build starts. After scope approval, new requests go to the next Function Cycle. Every request is classified within 24 hours so you always know which side of the line it lands on.
We commit to a 48-hour scope SLA and Day 7 MVP. We need 48-hour feedback turnaround on your side. The 6-week build depends on it — every blocked decision compounds. If feedback consistently takes longer, the SLA pauses (in writing, with the days flagged).
Everything yours on delivery. We retain no licenses, no rights. Source, infrastructure, deployment, knowledge wiki — all transferred. If we ever part ways, the system continues to work as intended.
Most founders try to solve operational chaos by hiring an ops manager. It is the most expensive option, the longest runway, and the one that fails most quietly when the person leaves. Here is the honest comparison.
No pitch. No proposal. We talk about your business, identify the leverage, and tell you honestly whether what's above is the right answer for you.