Frequently asked
The questions people actually ask on the first call.
If the answer you need isn't here, ask us directly. We would rather tell you something inconvenient early than discover it together halfway through a build.
Cost and timelines
It depends on scope, but we quote a number before you commit, and it includes monthly running cost. A focused internal tool is a matter of days to weeks; a full platform with cloud, security and support is a multi-month engagement. We would rather give you a real range on a 30-minute call than a fake one on a pricing page.
Because the scope was small, the requirements were clear, and we used our own platform for the parts a person does not need to write by hand. A named engineer still reviewed everything before it went live. Large scope does not compress the same way, and we will say so rather than promise a date we cannot hold.
In writing, quoted before work starts on them. Nothing gets built on a verbal "can you just".
One decision-maker, access to the people who will use the software, and feedback within three working days of a demo.
Ownership, security and risk
You do. Repositories, cloud accounts, domains and data are created in your name or transferred to it. There is no lock-in clause in our contracts.
Yes, before any brief is discussed in detail.
Included. Our own security division reviews every release before it ships. Independent penetration testing for third-party systems is a separate scoped engagement.
Support and maintenance is a division, not an afterthought. Every build ships with a plan covering monitoring, patching, backups and a defined response window.
The company
Because we tell you the truth about our size instead of padding it. Two systems are in daily use, our own product runs in production, and the founders are on every call. Ask for a paid pilot before committing to anything large — we would suggest it ourselves.
No. Most engagements start with one or two. The point of having ten is that when you need the eleventh thing, you do not have to go find a new vendor.
Yes, remotely, with overlapping hours agreed at the start of the engagement.
Often, yes. We start with a paid architecture review so we can tell you honestly whether it should be fixed or replaced. Sometimes the answer is leave it alone, and we say so.
Still have a question?
Ask it on the first call. There is no charge for a working session and no obligation afterwards.
