Question 1

How accurate is the estimator?

Accepted Answer

It is a range, not a quote. It is built from the hours similar projects actually took, so it lands in the right order of magnitude. After a scoping call we give you a firm number, which is usually narrower than the range rather than higher than it.

Question 2

Do you work fixed-price or time-and-materials?

Accepted Answer

Both. Fixed-price suits well-defined work such as an MVP with an agreed scope. Time-and-materials suits products that will keep evolving. We will tell you which one fits your project, including when fixed-price would cost you more.

Question 3

What is not included in the estimate?

Accepted Answer

Third-party costs you pay directly — hosting, app store fees, payment processing, paid APIs and licensed assets. We size these with you during scoping so there are no surprises.

Question 4

How do payments work?

Accepted Answer

Work is split into milestones with a payment attached to each. You pay as things are delivered, not up front. The terms are set out in our Public Offer Agreement.

Question 5

How long does a typical project take?

Accepted Answer

Most of our projects run three to four weeks from kickoff to launch. We keep scope tight on purpose so something real ships quickly; larger products then run in further short phases rather than one long build.

Question 6

What do you need from us to start?

Accepted Answer

A clear problem statement and one person who can make decisions. Designs, specs and research help, but we can run discovery with you if you do not have them yet.

Question 7

How do you keep us informed?

Accepted Answer

A shared board you can see at any time, a weekly written update, and a demo of working software every sprint. No status meeting required to find out where things stand.

Question 8

Do you work with our in-house developers?

Accepted Answer

Often. We can supply a full squad, or embed alongside your team to add specific skills. We adopt your conventions and review process rather than imposing ours.

Question 9

Which time zones do you cover?

Accepted Answer

Our team works across Central Africa Time and US Eastern, so we overlap with most of Europe, Africa and the Americas for a meaningful part of the working day.

Question 10

Who owns the code?

Accepted Answer

You do. On final payment all intellectual property transfers to you, along with the repositories, infrastructure accounts and documentation.

Question 11

What happens after launch?

Accepted Answer

You choose. We can hand over with documentation and a walkthrough, or stay on for maintenance, monitoring and small changes. We never hold your infrastructure hostage either way.

Question 12

Can you take over an existing codebase?

Accepted Answer

Yes. We start with an audit covering architecture, dependencies, security and test coverage, and give you an honest read on whether to build on it or replace it — including when the answer is that it is fine as it is.

Question 13

Where does AI fit into what you build?

Accepted Answer

Where it earns its place. Models are excellent at extracting, summarising and explaining, so we use them for assistants, retrieval and semantic search, and custom MCP servers. Anything that must be correct every time — eligibility, pricing, compliance — stays in tested, deterministic code, and the model only explains the result.

The questions people actually ask

Pricing & contracts

How projects run

Working together

Code & handover

Still unsure?