Tell us what you're building.
Share your project and we'll come back within one business day with an honest point of view on approach, scope and fit.
What happens after you send this
You hear back within one business day
A senior engineer reads every submission — not a sales queue. The reply covers whether the project is a fit, an initial point of view on approach, and what we'd need to put together a proposal.
A short scoping call, if it's a fit
For anything beyond a quick question, the next step is a call to understand the process or system as it runs today. That's usually enough to give a realistic delivery window before any formal proposal is written.
A written proposal with a real number
Fixed scope, a concrete delivery window, and the stack we'd use — not an hourly estimate range. You'll know what the engagement costs and how long it takes before committing to it.
Before you write in
What should I include in my message?
A sentence on the process or system you're trying to fix or build, and roughly where you are today — an existing spreadsheet, a manual workflow, an early-stage product idea. Specifics beat a general description; they're what let us give a useful first reply instead of a generic one.
Do you work with businesses outside Singapore?
Yes — the team is based in Singapore but engagements run across Southeast Asia, remotely by default. Regional integrations (payment rails, regulatory bodies like MyInvois/LHDN, local messaging channels) are something we design for, not adapt to after the fact.
Is there a minimum project size?
No fixed minimum. Some engagements are a full platform build; others are a single automation or a scoped fix bolted onto an existing system. Send the details and we'll tell you honestly whether it's a fit.
I'm not ready to commit — can I just ask a question?
Yes. Plenty of messages through this form are scoping questions, not signed engagements yet — a quick answer on whether something's technically feasible is a normal use of the form.