Questions, answered.

You don’t need to. Tell us what feels slow, expensive or risky, and we find the cause. That’s what the first stage is for: we interview your people, follow real tasks and review your systems, then write down what we found.

No. We need someone who knows how the work is done and someone who can decide. We explain every choice in plain English, and bring your IT team in early if you have one.

Nothing formal. A rough description of the problem, the tools you use and who would use a new system is plenty. Examples of the spreadsheets or forms you rely on help a great deal.

Usually. Most projects connect to accounting, payment, HR or records systems already in place. We check what each allows during the audit and tell you plainly if something should be replaced instead.

It depends on what we find, so we don’t guess before we’ve looked. After the first stage you receive a phased plan with a milestone date for each phase, and the portal shows where you stand against it.

Two projects with the same name can differ enormously in effort. We price once we understand the work, as a fixed fee per phase, so the figure you agree is the figure you pay unless you choose to change the scope.

It often does. Each change is written up as a request in the portal with its effect on cost and timing, and nothing changes until you approve it.

You pay by milestone, so you never pay far ahead of delivered work. The code, accounts and documentation are yours throughout, so another team could continue exactly where we stopped.

The portal shows the current stage, each milestone’s status and anything waiting for you, and you receive a short written update every week.

You do. It lives in a repository in your name, alongside your hosting and domains, from the first day. At handover you receive the credentials, documentation and runbooks needed to run it without us.

Yes, for routine work, because it’s faster. A person reviews every change before it’s merged, automated scans check for security flaws, and tests and documentation ship with each milestone.

In the UK or EU by default, or another region if your law or regulator requires it, under a data processing agreement.

In most cases, yes. Send it before the first call and we’ll return it promptly or flag any clause we need to discuss.

A warranty period covers defects. After that, a Care agreement keeps the system monitored, patched and backed up, with a ticket queue in your portal and a monthly report on what changed and what we recommend.

Yes. We build for handover from the start: standard tools, documented code and a handover session with your developers.

Yes. Each launch includes training for the people who will use the system, plus short written guides.

Yes. Meetings run by video, documents live in your portal, and contracts can be written for your jurisdiction.

A named project lead runs your project from first call to go-live, with our engineers and specialists behind them. Your AI case handler answers questions any time, in your language.

We work in English, and our AI consultant takes enquiries in Somali, Arabic, Swahili, Finnish and Swedish too. Meetings are set at hours that suit your time zone.

Yes. We respond to formal tenders, complete supplier questionnaires and supply security and data-protection documents.