Consulting / Custom Software
Software built for your problem, not the average of everyone’s.
Purpose-built tools for workflows that off-the-shelf software doesn’t fit, designed from process understanding, delivered iteratively, owned by you.
The problemWhy this keeps hurting
Off-the-shelf software is built for the average of everyone’s problem, which is why your team runs the real process in spreadsheets, duct-tapes five half-fitting SaaS tools together, and contorts its workflow to fit whatever the vendor imagined. Sometimes the right answer is configuration. Sometimes it’s genuinely custom. The expensive mistake is not knowing which.
Who it's forDoes this sound like your organisation?
Businesses with a niche workflow no vendor builds for. Teams paying for a stack of tools that each fit 60% of the job. Organisations whose systems don’t talk to each other, and whose people have become the integration layer.
How we workObserve · Decode · Redesign · Install
Observe
Discovery. We map the workflow the software has to serve: the real one, including the spreadsheet stage everyone forgets to mention.
Decode
Diagnosis. Build vs buy vs configure, called honestly. If an off-the-shelf tool fits, we tell you. It’s cheaper and we’d rather keep your trust.
Redesign
Design. A scoped, sequenced build plan: smallest useful version first, integrations mapped, ownership and hosting decided up front.
Install
Implementation. Working software delivered iteratively (your team using release one while release two is built), with documentation and handover, not lock-in.
What you getDeliverables, not decks
- An honest build-vs-buy assessment before any code is written
- Working software delivered in small, usable releases: value from the first iteration
- Integrations that retire the copy-paste work between your existing systems
- Documentation, handover and code ownership, plus optional ongoing support
Engagement shapeHow it typically runs
Typically 1–2 weeks. Workflow mapping and the build-vs-buy call, with a scoped plan either way.
Typically 1–3 weeks. Architecture, sequencing, and the smallest-useful-version definition.
Iterative releases from the first weeks; total duration scales with scope, reviewed at every release.
Durations are indicative and agreed per engagement. Pricing is discussed once we both understand the problem: no rate card theatre.
QuestionsAsked honestly, answered honestly
Why not just buy something off the shelf?
Often you should, and discovery exists to find that out before you pay for a build. We recommend custom software only when the workflow genuinely isn’t served by configuration or integration.
Who owns the code?
You do. Source, documentation and deployment are handed over as part of the engagement; ongoing support is optional, not a hostage situation.
What technology do you use?
Fit-for-purpose with a bias to boring: proven, maintainable stacks your future developers will recognise. The AI-heavy parts get the same discipline.
How does this relate to AFOS?
AFOS is what this service looks like productised: patterns we kept rebuilding for organisations, turned into a platform. If your problem is knowledge, decisions and outcomes, an AFOS discovery partnership may fit better than a one-off build.
Discuss the problem.
Tell us what keeps repeating. We'll reply personally with an honest read, including if this service isn't the right fit.
Discuss a project All consulting services