Process
How an engagement actually runs.
No account managers, no handoffs between teams. The people who scope the work write the code and answer the messages, from first call to the last release.
01 · 1–2 weeks
Discovery
We map the actual problem before writing a line of code: users, constraints, existing systems, what “done” means. Output is a scoped plan with a fixed architecture, not a vague estimate.
- What you see
- Working sessions with the engineers who will build it, and a written plan you can challenge line by line.
- What you get
- Scope document with acceptance criteria
- Architecture and data-flow outline
- Fixed price and timeline
02 · Weekly cycles
Build
Weekly demos of working software, not status decks. Every change ships behind typed contracts and automated tests, to the same rigour we hold our own products to.
- What you see
- A staging environment you can use at any time, and a demo of what changed every week.
- What you get
- Working software every week
- Automated tests with every change
- Architecture Decision Records as we go
03 · Fixed date
Launch
Monitoring and alerting go live with the product, not after an incident. Pre-launch checks cover the things that fail silently (data integrity, deletion flows, analytics) before real users touch them.
- What you see
- A launch checklist signed off with you, including a security review and a real restore test.
- What you get
- Production deployment and monitoring
- Runbooks for common operations
- Full handover of access
04 · Ongoing
Support
Direct access to the people who built it, not a ticket queue. We stay attached to what we ship: watching production, fixing what breaks, and scoping what comes next.
- What you see
- The same shared channel and the same engineers you worked with during the build.
- What you get
- Production watch and fixes
- Scoped follow-on work
- A team that already knows the system
Direct communication
A shared channel from day one. Questions get answered by whoever wrote the code, same day.
Fixed scope, fixed price
Discovery produces a real plan before commitment. No hourly drift, no scope surprises mid-build.
Senior-led, always
Every engagement is led end to end by senior engineers, and you always know exactly who is doing the work.
Questions
What clients ask before we start.
How is an engagement priced?
Discovery produces a fixed scope, architecture, and timeline before you commit to the build. The build is then priced against that plan: a fixed price, not an hourly estimate. Fixed-scope projects start from $10k; ongoing work runs on a monthly retainer.
What size of project is a good fit?
New products, rebuilds, and ongoing work where quality matters more than the lowest quote. Because we keep the studio small, we will also tell you honestly if a project is too large for us to do well.
How long does a typical engagement run?
It depends on scope, and discovery fixes the real timeline before you commit. A focused build is typically a matter of weeks, not quarters. Architecture reviews are delivered as a written position with the trade-offs named.
Who will actually work on our project?
The people you speak to on the first call. We do not hand projects to a delivery team, and we do not staff them with juniors.
Do you work with clients outside Sri Lanka?
Yes. We work remotely with clients anywhere, and our working day in Colombo overlaps comfortably with the UK and Europe. We schedule calls around your calendar, not ours.
How will we see progress?
Through working software. You get a weekly demo, a staging environment you can use at any time, and a shared channel with the engineers writing the code.
What happens after launch?
We stay attached to what we ship. Support covers watching production, fixing what breaks, and scoping what comes next, with the same people who built it.
Where is our data stored?
Wherever your users and obligations require, typically UK or EU regions. We design for data minimisation, real deletion, and a documented list of every sub-processor, so your legal team has answers before they ask.