Technology consulting and software development
We help mid-sized and large companies decide which systems to change, and change them.
We assess how your business and its systems work today, and plan what to change. Then we implement ready-made products where they fit, and build software where they don’t. AI strategy runs alongside, and every use of AI is judged on measured results.
A large company, simplified Example
What each service changes
Customers
- MarketingKeep
- SalesFix
- ServiceBuild
- Online channelsBuild
Operations
- PlanningFix
- Supply chainKeep
- FulfilmentBuy
- ProcurementKeep
Corporate
- FinanceKeep
- PeopleKeep
- Legal and riskKeep
- ReportingFix
Foundations
- DataFix
- IntegrationBuild
- InfrastructureKeep
- SecurityFix
Where are you starting from?
Six situations, in the words people use for them, with the first step that usually helps.
- Our systems grew piece by piece, and nobody has the whole picture.First stepAn assessment
- The board wants a technology plan with costs attached.First stepA technology strategy
- We have to replace a core system, and vendors are already pitching.First stepA software selection
- We bought the software, and it still isn’t working.First stepAn implementation review
- What we need doesn’t exist as a product.First stepA discovery for custom software
- We want AI to do real work, and show the result in numbers.First stepAn AI use-case assessment
Four services, and AI strategy alongside
Start at any of them. Each ends with a written result or software in use.
| Service | You get | Typical length | Priced as |
|---|---|---|---|
| Assessment | A current-state map, a ranked issue register, a cost and contract summary, and baseline measures. | Typical length4–8 weeks for one company or business unit; groups scoped company by company | Priced asFixed fee |
| Technology strategy | A target picture, a decision register, a roadmap with budget ranges, and a board summary. | Typical length4–8 weeks | Priced asFixed fee |
| Software selection and implementation | A shortlist tested on your scenarios, a five-year cost comparison and a decision memo. Then the product in use, measured against the baseline. | Typical lengthSelection 8–12 weeks; implementation set in the plan | Priced asSelection fixed fee; implementation by milestone |
| Custom software development | Working software in releases, with tests, documentation and a support plan, and the code in your repository. | Typical lengthDiscovery 2–4 weeks; first release 8–16 weeks after discovery | Priced asDiscovery at a fixed fee; building by release or by capped time |
| Alongside | |||
| AI strategy | A baseline, scored use cases, a pilot with a success line and a stop line, and a business case with the cost at volume. | Typical lengthUse-case assessment 3–4 weeks; pilot 4–8 weeks | Priced asFixed fee for the assessment and each pilot; production by release or milestone |
AI strategy
AI is held to the same numbers as any other investment.
We start from the work, measure it, and pick the few uses worth the effort. Before any pilot starts, four things are written down.
Before the pilot startsPilot sheet
- The baselineToday’s numbers for the task, measured the way the pilot will be measured
- The success lineThe result that justifies the next step
- The stop lineThe result that ends the pilot, and the date to decide
- The cost at volumeModel usage, checking time, monitoring, and what switching it off would cost
Sometimes the answer is a process change or a tool you already own. Then we say so.
What you receive
Every stage ends in documents you can use without us. Four samples show the format. Their figures are illustrative.
- Sample: issue registerAssessmentWhat is wrong, how much it matters, the evidence, and who owns the fix.
- Sample: decision registerTechnology strategyEach system with its decision (keep, fix, buy, build or retire), the reason, and the quarter work starts.
- Sample: five-year cost comparisonSoftware selectionThree shortlisted products on one basis: licences, implementation, integration, data migration, training and price increases.
- Sample: pilot sheetAI strategyBaseline, success line, stop line, decision date and cost at volume, on one page.
What we commit to in writing
Each of these is put in writing before work starts.
- After every stage you decide whether to go on, and you keep everything it produced.
- One named lead runs your engagement. If they have to be replaced, you agree the successor, and the handover is at our cost.
- Documents, accounts, data and code made for you are yours, and code lives in your repository from the first day.
- We sign a non-disclosure agreement before you share anything sensitive.
What we don’t do
- Day-to-day IT operations, hardware supply and round-the-clock support. When a project depends on them, the plan says so and we help you find a provider.
- Security testing, formal audits and certification. We flag where they’re needed and help you scope them.
- Legal advice. Contract terms stay with your lawyers.
- Acting as main systems integrator on programmes that need hundreds of people. On those, we work for you alongside the integrator.
Perspectives
Short notes on decisions that most technology programmes face. Each is dated and lists its sources.
Tell us what you’re trying to decide or fix.
A line or two is enough. We read every enquiry ourselves and reply within two working days.
What happens next
- We reply to arrange a call. If we’re not the right fit, we say so.
- A first call of 30 to 45 minutes with the person who would lead the work.
- A written proposal for the first stage: scope, deliverables, length and fee.
We can sign a non-disclosure agreement, yours or ours, before you share anything sensitive.