Start a project
Start a project conversation
Describe what you need and the scope gets clarified together. Your message is prepared the moment you pick a system type; it goes by email or WhatsApp, straight to the founder.
01 — What do you want to build?
Your message
Pick a system type — your message gets built here, and you can edit it however you like before sending.
Nothing to worry about
- Price is set by scope and modules; no price or timeline is quoted before the scope is clear.
- No spec required — a few sentences are enough for a first message.
- What comes back is a few concrete questions that clarify the scope — and a short call if useful.
- WhatsApp is enough for first contact; email just carries more detail.
Prefer to write without selecting? send an email directly.
What happens after you send?
01
Your message reaches the founder
No form queue, no support bot; the request is read by the person who would build the system.
02
Scope questions come back
A few concrete questions that clarify the need — a short call if useful.
03
You get a clear assessment
An honest read on scope, approach and the price frame; if it's not a fit, that's said plainly.
Before you send
Is a one-person brand risky?
Structure reduces the risk, not headcount: written scope, documentation, a transferable codebase.
How is the price set?
No fixed list; price is set by scope and modules — a clear quote once the scope is agreed.
How long does it take?
No dates before the scope is clear; a realistic frame is discussed with the scope.
What do I end up with?
A working system, a manageable panel, documentation and a clean handoff.
Do I need to know the technical details?
No. Explaining how the work runs is enough; the technical decisions get settled together in the conversation.
What if I'm not sure what I need?
“Not sure yet” is a valid starting point. Clarifying the need is what the first conversation is for.
Is WhatsApp enough for first contact?
It is. Start with a short message; if it needs detail we move to email. Both land in the same place.
What if my project is small?
A small scope stays small — it doesn't get inflated. And if it isn't a fit, that's said plainly.
What sets the scope?
Scope is drawn by how many screens and how many modules get built. The four factors below drive the scope — and with it the price. Which of them you actually need is agreed in writing in the first conversation.
- Screen and module count
- Depth of roles and permissions
- Integrations with existing systems
- Content management and panel needs
How I work
“Scope gets clear first; the solution is proposed after that.”
“I'd rather clarify vague work than inflate it.”
Still deciding?