Frequently asked
Pricing, timelines, ownership — answered plainly.
Team & Process
Yes. The person who scopes your project is the person building it. No account managers relaying messages back and forth — you talk to the engineer directly, from the first call.
We keep it to two or fewer active engagements per engineer. That is a deliberate limit, not a scheduling accident — it is how a four-person team keeps every project moving.
Tell us and we scope it. Small changes get folded into the current sprint; larger ones get priced and scheduled honestly rather than quietly stretching the original timeline.
Working software on a fixed cadence, not status calls. You will always be able to see and click through what has actually been built, not just hear that it is "on track."
Pricing & Payment
Projects start at $500, scoped to what you actually need. We agree on scope and price before any work starts — no hourly billing surprises.
Fixed for the agreed scope. If you want to add something mid-project, we price that separately and clearly, rather than letting it quietly inflate the original number.
No. Payment is structured around delivery milestones, not a single upfront lump sum. Details are agreed in writing before the engagement starts.
The starting price covers a scoped MVP build under our standard engagement. Ongoing hosting, third-party API costs, and work outside the agreed scope are addressed separately and disclosed upfront — never discovered at the invoice.
Yes, if you want one. Many clients move to a lighter monthly retainer after launch for ongoing support and iteration. It is optional, not a requirement to get the initial build.
Timelines & Delivery
A working MVP in 21 days is our standard commitment for a first build. We will tell you upfront if a timeline is not realistic for your scope, rather than agreeing to one we cannot hit.
If the agreed target has not been hit by day 21, we keep working the next sprint at no extra cost until it is — or you keep everything built so far and walk away. Either way, you do not lose.
The specific, measurable target we agree on together before the project starts — for example a conversion rate, a load time, or a task getting automated. We instrument it early so progress is judged on real numbers, not opinions.
Often, yes — tell us the date during scoping and we will confirm honestly whether 21 days gets you there, or what would need to change to make it work.
Ownership & Handover
You do, outright, from day one. Everything lives in your own accounts and repositories — no lock-in, and no dependency on us to keep it running.
During development. You get visibility from early in the build, not just after a final invoice clears.
Everything is documented and handed over in a way your own team — or a new one — can actually pick up and maintain. Designed to be left, not designed to trap you.
Both. Every engagement includes documentation alongside the build, not as an afterthought bolted on at the end.
Services & Scope
Both. Full-stack web and mobile development — iOS, Android, and web platforms — is one of our four core disciplines.
AI systems that handle real, repeatable work — customer support, follow-ups, research, data entry — running continuously without adding headcount. We scope it around one real task costing you time today, not a general "AI strategy."
Fintech and RegTech systems are one of our four core disciplines, alongside product engineering, AI automation, and Web3 infrastructure. Tell us your specific compliance requirements during scoping and we will confirm fit honestly.
Yes. We will review what exists first and tell you plainly whether it is worth building on or better to start fresh — before you commit to either path.
Sparky is our own one-click ecommerce product with built-in AI features, available for $20 lifetime — a ready-made solution, not a custom build. If you need something built specifically around your business, that is a separate scoped engagement.
Support & After Launch
Post-launch support is included for a defined window after handover, covering fixes and questions tied to what we built. Details are agreed upfront as part of scoping.
Reach out — most fixes are quick, and many clients keep a lightweight retainer specifically so this is already covered rather than a one-off scramble.
Yes — a large share of our work comes from clients returning for the next thing once the first engagement proves out.