Can two people actually do this?
+
For work that fits a written scope with a date on it, yes — that is exactly why the list of what we don't do is on this page. We are not staffed to run enterprise procurement or 24/7 on-call, so we don't sell it. What we do sell, we deliver ourselves, which is why there is nobody in between you and the build.
What actually happens if the date slips?
+
It goes in the written scope before you pay anything, and it is not re-estimated once work starts. You also see the thing running at the halfway mark, so a slip is visible to you with time to act rather than announced at the end. We would rather commit to a real date than pad the estimate — a padded estimate is just an agency timeline with better manners.
Why isn't pricing on the site?
+
Because a real number needs a real scope, and we won't quote one without the other. The call is thirty minutes and ends with a written price and a date. Nothing about that is a sales process — you keep the document either way.
Who owns the code?
+
You do. Outright, from day one, in your own repositories and your own accounts. No licence, no hostage hosting, no per-seat fee to keep using the thing you paid to have built.
What happens after it goes live?
+
Most clients keep the Operator Retainer — hosting, support, changes, new reports and priority access. It is cancel-anytime. If you would rather take it in-house, the code and the accounts are yours and we will hand over cleanly.
What if the scope changes mid-build?
+
Small things get absorbed. Anything that moves the date gets written down, priced, and agreed before we touch it — so the date never quietly moves while you assume it hasn't.