Questions we are asked before every engagement.

Evaluate four things: relevant delivery experience in your sector, the seniority of the people who will actually do the work, how they handle change and disagreement, and what happens after launch. Ask for two references from engagements that went badly at some point — how a partner behaves under pressure tells you more than a polished case study. Our own capabilities span:

• Web and mobile application development
• Software architecture and system integration
• IT consulting and independent audit
• Legacy system modernisation
• Cloud migration and platform engineering
• QA, testing and accessibility
• Business analysis and discovery
• Managed support and IT staffing

A firm that builds software specifically for one organisation rather than selling a product to many. Unlike off-the-shelf tools, a custom system is designed around your existing processes, integrates directly with the systems you already run, and belongs to you — including the source code and the infrastructure it runs on.

With a paid discovery of two to four weeks. We map the current state, agree what success looks like and produce an architecture, a delivery plan and a costed phase one. If you choose not to continue, all of that documentation is yours.

Both, though the shape differs. Enterprise work is typically modernisation, integration and compliance. Startup work is usually a first production build with a small senior team. What we do not take on is work where the budget only supports junior delivery — it does not end well for either side.

It depends on complexity, integration surface and the compliance environment. As a guide: a focused product build generally runs $60,000 to $250,000; platform modernisation for an enterprise typically starts around $400,000; a discovery phase is $15,000 to $40,000. We quote per phase so you can stop or redirect at each boundary.

It usually is not, and we will say so. Off-the-shelf wins when your process is standard and the product covers it. Custom wins when the process is a genuine competitive difference, when integration requirements make configuration impossible, or when licensing at your scale costs more than building. The honest test is whether your workarounds are already costing more than the build would.

Change requests are estimated within the same sprint and priced against an agreed rate card. Nothing is built without written approval, and nothing gets absorbed silently into the schedule. You see the revised date and cost before deciding.

Monthly in arrears against a signed statement of work, net 30. Fixed-phase engagements are milestone-based with a holdback until acceptance. We do not ask for large upfront payments.

You do, from the first commit. Repositories, cloud accounts and CI pipelines are created in your organisation and we work inside them. There is no dependency on us to access, deploy or change your own system.

Yes, and roughly half of our work is exactly that — embedded delivery with a shared backlog, shared standards and shared on-call. We are equally comfortable owning a workstream end to end where you do not have the capacity.

Delivery teams are in the Americas, Europe and South Asia. Every engagement has at least four hours of overlap with your working day, agreed before we start.

A written weekly report covering what shipped, what is at risk and what decisions we need from you, plus a demo at the end of each two-week increment. You also have direct access to the team's channel — no gatekeeping.

Secure development practices are built into the pipeline: dependency scanning, static analysis and secret detection on every commit, plus penetration testing before a production launch. Our engineers work under NDA with background checks where a client requires them.

We deliver against SOC 2, HIPAA, PCI DSS, GDPR and ISO 27001 requirements. We are not an auditor and do not issue certifications, but we build to the controls and produce the evidence trails your auditors will ask for.

We work with anonymised or synthetic data wherever possible. Where production data is genuinely required, access is scoped to named individuals, logged, and revoked at the end of the phase — under a data processing agreement signed before any access is granted.

Yes. Support agreements range from business-hours cover to 24/7 on-call with contractual response and resolution targets. Every retainer includes a reserved pool of engineering hours each month for enhancements, so small changes do not need a new contract.

Frequently. We run a takeover assessment first — dependency inventory, monitoring gaps and a tested restore — so both sides understand the condition of the system before an SLA is agreed.

That is a normal and reasonable outcome, and we plan for it. Handover includes documentation, runbooks, architecture decision records and a transition period where our engineers pair with yours. We have no interest in being difficult to replace.