What we take on.

Legacy takeover

We take over the software other people built.

The vendor left. The developer moved on. The documentation was never written. You still have a system your business depends on, and nobody who understands it. That handover, the one nobody planned for, is our core work.

Every takeover starts with the audit. We read the code, map the infrastructure, and trace the costs. Then we tell you the truth about what you have: stabilise it, extend it, or rebuild it. Rebuild is the recommendation only when the audit supports it. RoloNext came to us as a full rewrite; the audit showed the app only needed a refactor. That advice is the product.

What you get

• A written audit finding: the state of the code, the infrastructure, and the running costs.
• A clear recommendation with the reasoning attached: stabilise, extend, or rebuild.
• A fixed-scope plan and price for whichever path you choose.
• A team that has done this before. Natshoot, Hunters Portal, and GolfPlayed all began as systems someone else built.

The audit

Advice first. Work second.

The audit is a standalone engagement with a standalone deliverable. If the finding is that your system is fine, that is what the finding says, and you owe us nothing further. Most clients continue into the work; none are obliged to.

What you get

• Code review: structure, quality, risk, and what it would take to change safely.
• Infrastructure review: architecture, security posture, and where the hosting bill goes.
• The written finding: stabilise, extend, or rebuild, with what each path costs.

Dedicated team

Senior capacity, embedded in yours.

When you have the roadmap and need the hands, we place senior engineers inside your team. Same people for the duration, no rotation, no bench swaps. This is how our Embedded plan runs day to day.

What you get

• Senior engineers only. The people who scope the work do the work.
• Continuity by contract: the same team from the first sprint to the last.
• Your process, your repos, your standards.

Built from scratch

New systems, when new is the right answer.

Takeovers are the specialty, not the ceiling. We design and build systems from scratch: member platforms, field service tools, internal systems, and the public websites that front them. FUCHS field reporting was built this way, from a blank page to a working data asset.

What you get

• Business analysis first: how the work actually happens, mapped before a line of code.
• Fixed scope, delivered fast, by senior engineers only.
• The run: hosted, watched, and supported on one monthly number.

Data and reporting

The numbers you already have, somewhere you can read them.

Most businesses are not short of data. It is just spread across an accounting package, a spreadsheet one person maintains by hand, and the system we built or took over. Nobody can answer a straight question without three people exporting something first.

We connect those sources and turn them into reporting you can act on. Into Power BI where you already license it, into your own system where the numbers belong beside the work, or into whatever platform you have already standardised on. The tool matters less than the pipeline behind it being reliable, which is why this runs inside a build or the monthly run rather than as a separate engagement. Reporting is only as good as the systems feeding it, and keeping those working is already our job.

What you get

• Integration with the systems you already run, accounting and operational, spreadsheets included.
• Reporting built where you will actually look at it: Power BI, your own system, or the platform you already use.
• Figures that refresh on their own, so nobody rekeys anything to answer a question.