Skip to content
Questions

Answers, plainly put

How we scope, what we charge, who owns the code and what happens after launch.

Process

With a conversation, not a quote. We want to understand the workflow you have today — including the parts that happen in WhatsApp and on paper — before proposing anything.

After that you get a written scope with acceptance criteria, a timeline and a fixed price. Nothing is built until you agree to that document.
A focused tool is usually four to six weeks. A full platform with payments and an admin portal is typically eight to fourteen weeks.

You see working software on a staging URL every week, so you are never waiting until the end to find out what you are getting.
Yes, and often that is the right arrangement. We can build a module inside your codebase, review your team's work, or take on the part nobody on the team has time for. We follow whatever conventions your repository already uses.

Pricing & contracts

Fixed price for defined scope, or a monthly retainer for ongoing work.

Fixed price means the number in the scope document is the number you pay — if we underestimate, that is our problem, not a change order. Scope changes are quoted separately before any work starts on them.
Typically 40% to start, 30% at the mid-point demo and 30% on delivery. For retainers, monthly in advance. Larger projects can be split across more milestones.

Security & ownership

You do, completely, from the first commit. The repository is yours, the server credentials are yours, and there is no licence you need to keep paying for.

If you ever want to move to another team, everything they need is already in your hands.
Two-factor authentication is enforced on every administrator account. Credentials for third-party services are encrypted at rest. Sensitive records carry an audit trail, and dependencies are patched on a schedule rather than when something breaks.

On request we will run a security review before launch and give you the findings in writing.

Support

Thirty days of support are included with every project — bugs in what we built are fixed at no charge.

After that, most clients take a maintenance retainer for patching, backups, monitoring and a priority ticket queue. It is optional; you are not locked in.
It depends on priority. Urgent — a system down or money at risk — is two hours. High is eight hours. Normal is one business day, and low priority is three.

Every ticket shows its target on your tracking page, so you can see the clock we are working against.

General

We are a remote-first studio working with clients across East Africa and further afield. In practice it changes nothing: work happens on a staging URL you can open from anywhere, demos are on a call, and the support desk does not care where either of us is sitting.

Still have a question?

Ask it directly — a real engineer answers, usually the same day.

Prefer email? primarch.admin@gmail.com