Grab a 30-minute slot.
Three things that always happen.
We’re a small studio. There’s no SDR layer between you and the people who’d build your system.
No autoresponder. Mas reads every inbound and writes the first reply.
30 minutes. We’ll ask what’s painful, what you’ve tried, and what shape a fix could take.
If we’re the right partner, we’ll say so. If not, we’ll often know who is.
Common questions, honest answers.
Do you take small projects?
Yes. Smallest engagements ship in 1–2 weeks. If a project genuinely belongs as a Zapier flow rather than a custom build, we’ll tell you.
How fast can you start?
Discovery calls usually happen within a week of inbound. If scope is clear after that, we can be building within ten days.
What if my brief is messy?
That’s the discovery call. You bring the chaos; we’ll structure it. Most engagements start as a one-page spec we write together.
Do you do ongoing support after launch?
Yes. Most builds move into a monthly maintenance and iteration arrangement — because operations don’t hold still and neither should the system that runs them.
Where are you based, and where do you work?
Melbourne, Australia. We work async with clients globally. Timezone alignment matters for live calls; otherwise the work happens on Loom, in the portal, and in code.
What stack do you use?
Boring stacks with sharp opinions — React/Next.js, Postgres/Supabase, n8n and Make for automation, custom code where it earns its keep. More on the About page.