The kinds of project we take on.
Real categories of work, described as they actually run — what each build contains, how long it takes, and what it changes for the business.
Last updated
Software development project types
- Restaurants · Mobile + Web
Food Delivery Platform
A restaurant group’s own delivery operation: customers order in an app, riders are dispatched and tracked, the kitchen works from a screen, and head office sees every branch at once.
- 4
- connected apps
- 10–16 wks
- typical build
- iOS + Android
- plus web dashboards
- Retail · E-commerce
Online Store & Order Management
A store customers can buy from quickly, connected to accurate stock, with a back office where the team processes orders, refunds and returns in one place.
- 1
- accurate stock figure
- 6–12 wks
- typical build
- Shopify or custom
- chosen on your catalogue
- Service businesses · AI
AI Receptionist & Call Handling
A phone assistant that answers every call, books appointments into the real calendar, and passes anything unusual to a person with the caller’s details already captured.
- 24/7
- call coverage
- 3–6 wks
- typical setup
- Every call
- logged and searchable
- Professional services · Web
Customer Portal & Web Application
A secure area where customers see their own orders, documents, invoices and requests — and stop calling to ask for things they could look up.
- 24/7
- self-service access
- 8–14 wks
- typical build
- Role-based
- permissions throughout
- Startups · Product + Cloud
SaaS Product Build
A subscription product taken from idea to paying customers: the application itself, the sign-up and billing around it, and hosting that holds up as usage grows.
- 3–5 mo
- to a paid launch
- Every 2 wks
- something you can use
- 100%
- code and IP yours
- Services · Custom software
Booking & Scheduling System
Online booking that respects your real availability, staff and resource scheduling behind it, and automatic reminders that cut no-shows.
- −No-shows
- automatic reminders
- 6–10 wks
- typical build
- Multi-site
- staff and resources
Software development projects: what each type involves
The six entries below are categories of build rather than individual client engagements, and it is worth being direct about why. Naming clients and quoting measured results requires permission we have not been given for every project, and a case study nobody can verify is worth less than an honest description of the work. So each page describes what a project of that kind actually contains, how long it runs, what it is built with, and what changes for the business once it is live.
They differ from each other more than the labels suggest. A booking system is one application with one kind of user and a calendar underneath it. A food delivery platform is four applications — customer, rider, kitchen, owner — that all have to agree with each other in real time, which is why it takes three times as long. A SaaS product carries something neither of those does: other people's customers, billing, and the operational load of being the supplier rather than the buyer.
The table below puts the six side by side on the two things people ask first — how long, and how many separate pieces of software are involved. Both are ranges quoted before we know the detail, and both get firmer once we do.
How long does each type of software project take?
Ranges quoted before we know the detail, and the reason two projects that sound alike in a sentence can differ by three months.
| Typical buildFirst call to live | Applications involved | What moves the price most | |
|---|---|---|---|
| Food delivery platform | 10–16 weeks | Four: customer app, rider app, kitchen screen, owner dashboard | Number of branches, and whether riders are yours or a courier service |
| Online store & order management | 6–12 weeks | Two: storefront and stock or order back office | Catalogue size, and how many systems the stock figure must agree with |
| AI receptionist & call handling | 3–6 weeks | One, plus connections to your calendar and CRM | Call volume, and how much your team needs the assistant to know |
| Customer portal & web application | 8–14 weeks | One, plus an admin side for your team | How many roles and permissions, and what it has to read from |
| SaaS product build | 3–5 months to a paid launch | Two: the product and the billing and account layer | Multi-tenancy, billing rules and how much you launch with |
| Booking & scheduling system | 6–10 weeks | One, plus a staff or resource view | Sites, staff and resources, and how complicated availability really is |
What people ask about these projects.
Are these real client case studies?
No, and we would rather say so than imply otherwise. They describe categories of work we build, with indicative scope and timelines. Named clients and measured results appear here only once we have permission to publish them, because an unverifiable case study helps nobody.
How long does a software project take?
Between four weeks and six months, depending on how many applications are involved and how much has to connect to systems you already run. A single web application sits at the fast end; a multi-app platform with live logistics sits at the slow end.
What makes a project run over?
Usually one of three things: a decision that takes six weeks to make, an integration with a system nobody has documented, or scope that grows quietly because nobody priced the additions. We name the likely three at the start of every project for exactly this reason.
Can we start with a smaller version first?
Yes, and it is usually the better purchase. Most of these break into a first release that solves the expensive part of the problem and later stages that add the rest. You find out whether the thing works before committing the whole budget to it.
What do we need to have ready before starting?
Less than most people expect. A clear description of the problem, one person able to make decisions, and access to whatever exists already — the current system, the reports, the spreadsheets holding things together. We work the rest out with you in the first stage.
Tell us what you need built.
A free 30-minute conversation about your project — no presentation, no pressure. You will have a written plan and a real price within 48 hours.
Start a ProjectReply within one business day · You own everything we build · No lock-in