Two days. A working prototype. An architecture you can pressure-test.
For prospects who’ve done the diagnostic, run the estimator, even completed discovery — but want to see the system actually work before committing to a full build. S$5,000–S$8,000 depending on surface complexity.
A workshop for the team that owns the work
The session is designed for the operators who know where the spreadsheet, WhatsApp thread, and manual handover break.
Some prospects can’t commit to a full build yet — and they shouldn’t have to.
Discovery produces a written plan. A full build ships a complete system. Between them is a gap: the prospect who wants to see one surface actually working — a real pricing engine, a real supplier portal, a real production tracker — before signing for the full build.
The Architecture Workshop fills that gap. Two days of focused work. One surface prototyped end-to-end on a staging URL the prospect can pressure-test internally. An architecture document covering the full system that prototype hints at.
At the end, the prospect either continues to the full build with real evidence the approach works, walks away with the prototype code and architecture, or pauses with a clear decision rather than a vague one.
Three deliverables, not a slide deck.
One workflow surface, end-to-end, on a staging URL.
Usually the pricing engine, the supplier portal, or the production tracker. Real data shapes. Real auth. Real flows. Your operations team can log in and try it the same week.
The full system mapped, even though only one surface ships.
Data model, portal structure, integration surface, role permissions, mobile considerations. Detailed enough that any competent dev team could continue the build.
Clear path forward — yes, no, or pause.
A written recommendation: continue to full build with adjusted scope, walk away with the prototype as a learning, or pause until a specific trigger event.
The right prospect for the workshop.
- You’ve completed discovery (with us or anywhere) and you want to see one surface working before committing to build.
- Internal stakeholders need to pressure-test the approach before approving the full budget.
- You want a hedge against partner risk — at the end of the workshop you have a working prototype and an architecture doc, even if you walk away.
- You have one specific surface in mind already — pricing, supplier portal, production tracker, document automation.
- You haven’t mapped the workflow yet — run discovery first.
- You’re ready to commit to a full build — go straight to it; the workshop adds cost without speeding the outcome.
- You expect the workshop to produce a complete system — it produces one surface, by design.
- Your scope is too vague — "we need an ERP" is not a workshop scope.
Workshop, discovery, build — the right next step is the one that matches your decision risk.
WhatsApp in SG business hours routes to a human in under an hour.