016–10 weeks
Point of sale & retail
Offline-first tills that keep selling when the connection drops, then reconcile themselves.
Till app for existing hardware
Stock and multi-branch transfers
Day-end and month-end close
Local tax and currency rules
Services — six ways we engage
Software built to run a business, not to demo well.
Two engineers, one scope, a fixed price agreed before anyone writes code. You talk to the people building it for the whole engagement.
18
Systems shipped
6w
Typical first release
02
People on your project
1d
Reply time
What we do
Each engagement is scoped, priced and dated before it starts. No open-ended hourly work.
Scope this
028–12 weeks
Booking & reservations
Direct booking engines for hotels, villas and tour operators — no per-booking commission.
Rates, availability and blackouts
Channel and calendar sync
Card and bank payment capture
Front-desk check-in flow
034–8 weeks
Internal tools & dashboards
The system that finally retires the spreadsheet a whole team is quietly depending on.
Role-based admin and permissions
Import from existing sheets
Reporting your finance team accepts
Full audit trail
0410–16 weeks
Product builds from zero
A founder with a market and no engineering team. We scope, design and ship version one.
Scope workshop and written spec
Design system and UI
Full build, tested and deployed
Handover docs and training
052–5 weeks
Integrations & automation
Two systems that refuse to talk, and the person copying data between them every morning.
API and webhook integrations
Scheduled sync jobs
Data migration and clean-up
Failure alerting
06Monthly
Support & maintenance
What happens after launch, written down — so nobody wonders who to call at 9pm.
Uptime and error monitoring
Agreed response windows
Small features each month
One written monthly report
How an engagement runs
Four steps, the same every time. You know what happens next and what it costs.
01
Call
Thirty minutes on the problem. We say plainly whether we are the right studio for it.
Day 0
02
Scope
A written spec: screens, data, integrations, what is explicitly out. Fixed price attached.
Week 1
03
Build
Weekly demo on a real URL. You use it as it grows — no six-week silences.
Weeks 2–10
04
Hand over
Deployed, documented, your team trained. The code is yours, in your repository.
Launch week
Engagement models
Pick the shape that fits the problem. All three are fixed in writing.
Most projects
Fixed-scope build
One agreed scope, one price, one date. Changes are quoted separately rather than absorbed silently.
Priced after scope · 50 / 50 payment
After launch
Monthly retainer
A fixed block of hours each month for fixes, small features and monitoring on a system we built.
Rolling monthly · 30 days notice
Before you commit
Advisory sprint
One week of review on an existing codebase or plan, ending in a document you can hand to any team.
One week · flat fee
What we build on
A deliberately small stack. We can hand any of it over to your own team.
Frontend
Next.js · React · TypeScript · Tailwind
Backend
Node · Rust · Python · Postgres · Drizzle
Mobile
React Native · Expo
Infrastructure
Vercel · Fly.io · Supabase · Cloudflare
Tell us the problem, not the spec.
A 30-minute call is enough for us to say whether we're the right studio — and what it would cost.