CUSTOM SOFTWARE
We build systems around how your business actually works. It starts with understanding the process, not with choosing a technology.
No cost and no obligation until we agree a scope and a price.
WHO IT IS FOR
Custom software is the more expensive answer. It is the right answer when the alternative is paying people to be a database.
How you quote, schedule or reconcile is the thing that makes you money. Bending it to fit a package would cost you the advantage.
One file, twelve tabs, three people who know how it works and one who maintains it. It runs the business and nobody can leave.
The accounting package stays. The ERP stays. What you need is the layer that sits between them and the work you actually do.
WHAT YOU GET
Every custom engagement produces these, and the first two are yours whether or not you build with us.
SCOPING
Six questions, about five minutes. You will get an initial response within one business day — from a person who has read your answers.
Loading the scoping form…
HOW IT RUNS
The written scope is yours either way, and you may take it to another developer. Once it is signed, the build follows the same seven-stage protocol as every Silverconne delivery.
3–5 days
An engineer reads your six scoping answers and replies within one business day, then spends time with the people who do the work, not only the people who manage it.
Fixed-price written scope
Features, exclusions, integrations, migration, a fixed price and a delivery date, in one document you approve.
Weekly live demos from week 1
Short cycles with a live demonstration every week. You use the system while it is being built and change your mind early, not late.
After-hours migration
Data is migrated and reconciled outside working hours, so your team starts the next morning on the new system.
In person, by role
Each role is trained on the screens it uses, at your premises, with your own data.
Named engineer on WhatsApp
One engineer who knows your configuration, reachable directly, with three months of support included.
Quarterly architecture reviews
Every quarter we review usage, performance and the next most valuable thing to build.
WORK SAMPLES
Fleet telemetry, an international events platform and an offline-first mobile app we built, and what each one changed.
AI-assisted vehicle tracking and fleet telemetry system
A real-time GPS fleet telemetry, driver tracking and fuel and maintenance capture platform, with AI route-deviation alerts and automated weekly cost reporting.
Full fleet visibility on one live dispatch screen, and per-vehicle cost-per-kilometre reports delivered weekly, within 5 days of month end.
Global events booking and delegate management platform
A high-concurrency international events booking portal with real-time seat and tier allocation, automated multi-channel confirmations, digital check-in passes and organiser analytics.
Global delegate registration with instant automated ticketing, zero double-bookings and real-time attendance dashboards.
Bible Hymns cross-platform mobile application
A lightweight, offline-first mobile application with instant full-text and hymn-number search, vernacular and English hymn indexing, adjustable typography and zero-latency local storage.
Fully offline operation on Android and iOS handsets, with sub-second hymn retrieval nationwide.
PRICING DETAIL
Precision architectural scoping and fixed-price governance: your number is set in a written scope, not on a web page. These are the five things that move it, in the order they move it most.
The bands we work in
Most projects land in the middle two bands. If yours is the first band, a product subscription or a website package is probably the better buy, and we will say so on the call rather than after the invoice.
One system to talk to is a week. Four systems, two of them undocumented and one of them a desktop application, is a month.
A clean export is days. Twelve years of spreadsheets with three spellings of every customer name is the single most common overrun.
One role is one interface. Six roles with different permissions and approval routes is six interfaces and a permissions model.
If two managers describe the workflow differently, the first cost is agreeing it. That is a real cost, and it is cheaper before the build.
Compressing a timeline means more people on the work, and more people on the same work is more expensive per unit delivered.
QUESTIONS
Because any number we produced from a form would be wrong, and a wrong number either loses you the project or loses us money on it. The scoping conversation gives you a fixed price you can hold us to.
A demo at the end of every second week from the start of the build. The first one is deliberately rough — it exists so you can tell us early that we have misunderstood something.
They will. Small changes inside the agreed scope are absorbed. Anything that moves the scope is priced as a written change before we do it, so the number never moves without your signature.
Postgres, TypeScript and a managed host, unless there is a reason not to. We choose it at the scope stage and we tell you why, because the technology is our problem and the outcome is yours.
Often. We start with a paid two-day review that tells you what state it is in and what it would cost to keep. If rebuilding is the better investment, the review shows the working.
Three months of support is included. After that, a support agreement with a named contact and agreed response times, or you take it in-house with our documentation. Both are fine.
Data residency, ownership, security and exit are answered once for every service in Architecture & Governance
NEXT STEP
Six questions, about five minutes. A consultant reads every answer and replies within one business day.
No obligation, and no cost, until we agree a scope and a price.