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. Discovery and workflow audit free. After commit, refund tiers protect every stage: 95% back after scope, 70% after MVP.
30 minutes. Your business, your bottleneck, whether what we build is the right answer. No pitch. If we are not a fit, you hear it on the call.
About an hour, together. Tools, data, manual processes. The audit identifies which workflow becomes the automation, which data feeds the dashboard, where the friction lives. Commit here and scope begins.
48 hours. Deliverables, timeline, cost, assumptions; every Function and Enhancement bundled. No vague statements of work. We meet to agree. Cancel here: 95% back.
Operational dashboard live on real data: revenue, pipeline, team capacity, client health. Not a mockup. Not a demo. Two iteration rounds, in your environment, behind authentication. Cancel after MVP: 70% back.
Six weeks from scope. Four functions complete: operational dashboard, workflow automation, AI assistant, notification centre. Plus hosting, authentication, database, agreed data connections. Miss any milestone: SGD 200 back per day late. Written into the agreement.
Code, infrastructure, SOPs, knowledge wiki: every artefact yours. No licenses retained. From here, two paths, switch any time. Function Cycles (SGD 2,400) add capability on the same 48hr / Day-7 / 6-week cadence. Maintain Mode keeps it supported: hosting, updates, AI refresh, async.
Same four functions every Foundation Build. Built around your data and workflows. Same architecture, same commitments.
Revenue, pipeline, team capacity, client health. One view. Role-based from day one. Goes live Day 7 as MVP.
One workflow chosen in scoping. Compliance chains, data-to-PDF, intake forms, review pipelines. The hour-eater, gone.
Plain English. "Who's overdue?" "Pipeline this month?" Answers from your live data, in seconds, with citations to the records.
Thresholds you set. Revenue dips, client risk, capacity flags, deadlines. No noise. Only signals you asked for.
Hosting, authentication, database. 2 to 3 data connections from scoping (finance, calendar, email, one business-specific). Knowledge wiki initialised: SOPs, roles, decisions, rules; cross-linked, searchable from the AI assistant.
Foundation done. Keep building, or settle in. Most clients run cycles, then maintain; open a cycle when 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. After any Function Cycle: no penalty. Work delivered is yours.
Enhancements bundled before build. New requests after approval go to the next Function Cycle. Every request classified in 24 hours.
Our 48-hour scope SLA and Day 7 MVP. Your 48-hour feedback. If feedback runs longer, the SLA pauses, in writing, days flagged.
Source, infrastructure, deployment, knowledge wiki. All transferred on delivery. No licenses retained. If we part ways, the system keeps working.
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.