How long does it take to build custom software?

Custom software builds at Kazap Technologies have taken three to six months from analysis to launch, including testing and user training: three months for a native iOS and Android app, six for a fintech marketplace using Companies House and HMRC data. A prototype comes first, so you can see whether the idea works before paying for version one.

Custom software & integrations | Kazap Technologies

What we do

Custom software is software built for one business's process, rather than bought off the shelf and bent to fit. We build web apps, internal tools, customer portals and native iOS and Android apps, and the integrations that let them work with the systems you already use. In the UK this is still often called bespoke software. We choose the technology once the problem is clear, and we host and support most of what we build after launch.

Client builds have taken three to six months each. A legal-document subscription platform guides users through each document, pre-fills it from saved data and produces a digitally signed PDF; it took three months, in Ruby on Rails on AWS. A prepaid legal-services platform for a start-up law firm sells fixed-price documents and books the solicitor in the same flow, with a payment gateway; five months. A private-share marketplace for a fintech start-up pulls each listing's company data from Companies House, HMRC and Royal Mail; six months. A native app for parents coordinating school runs stored only a name and an age for children under 13, and passed Apple's App Store review on that basis; three months.

Integration work connects what you already pay for: payment gateways, solicitors' calendars, and UK government data such as Companies House and HMRC. Kazap also builds its own products, including YLB Score, a free 0–100 audit of a local business's website, live since September 2026, and the Churrascômetro barbecue app.

What you get

Requirements and a data model you have signed off
Working, tested software for web, mobile or both
Integrations with the systems you already use
Training for the people who will use it
Hosting, support and maintenance after launch

Prototype → pilot → version one

We build in three stages, each ending in a decision, so you never pay for version one of an idea a prototype could have ruled out.

Prototype (proof of concept, or PoC). A clickable mock-up or a thin working slice that answers one question: does this work for your people and your data? Advisory engagements stop here, with a cost estimate.
Pilot. The real system with a small group of real users for a fixed period, against success criteria agreed in advance. Our lease and licence platform ran as a trial with two London landlords. At the end, go or no-go.
Version one (minimum viable product, or MVP). The smallest version your business can rely on every day: tested, with users trained, hosted and supported.

How it runs

Analyse. Requirements, architecture and data model. Gate: you sign them off before any code is written.
Prototype. Gate: go or no-go on the build, with a cost estimate in hand.
Build and test. Gate: you accept the software against the signed-off requirements.
Train and launch. Gate: the launch date is agreed with the people who will use it.
Host and support. Fixes, updates and changes after launch, from the person who built it.

Who it is not for

Anyone whose needs an off-the-shelf product already meets. We will tell you to buy it before we quote.
Marketing websites and online shops. We build the systems a business runs on.
Teams looking for extra developers to work through a ticket backlog (staff augmentation). We start from the problem, not the ticket.