Start a project
Tell us what you need built.An engineer reads it.
Five short steps, no sign-in, and no sales layer on the other side. Your brief goes straight to the founders of a software engineering company with 20 systems live across Brazil, Australia, India, the USA and Europe, and the person who replies is the person who would build yours.
- No account needed
- NDA by default
- Reply in one business day
Step 1: System
What are you trying to build?
After you send it
Three things happen,and none of them is a discovery call
It reaches a founder, not a queue
The brief lands in the founders' Telegram the moment you send it. Nobody triages it, scores it, or drops it into a nurture sequence.
An engineer answers
Usually inside a business day, with questions about the problem rather than a link to somebody's calendar.
You get scope in writing
If it is a fit, you get phases, architecture and an estimate you can hold us to: yours to keep whether or not you build with us.
Before you write
The questionseveryone asks first
How long does it take to hear back?
Usually within one business day. Your brief goes straight to the founders: there is no sales team triaging it first, and the engineer who replies is the one who would build the system.
Do I need to sign in to send a brief?
No. Fill it in and send it. Signing in is only useful if you want to save a draft and come back to it.
Do I need an NDA before I describe the project?
No. Confidentiality is our default position, which is why most of the work we deliver is never named publicly. Send an NDA if you want one on file, but do not wait on it to describe the problem.
What if I do not know my budget yet?
Say so. We will scope the work and come back with a number you can hold us to, along with what we would cut if it needs to be smaller.
Who owns the code?
You do, from the first commit. We work inside your repository and deploy into your cloud account under your keys, not into a hosted black box you rent back from us.
What happens if the project is not a fit?
We tell you, with reasons, rather than learning on your budget. The scope and architecture from a first conversation are yours either way.
Not ready for a brief?