Software architecture services
Choose the situation, not the technology.
Diagnosis
Architectural system review
The system works — or it doesn’t — and by now nobody knows why.
A map of the system and a list of the places that are expensive to touch, each with its price. Delivered as code audit services and software audit services on a running system.
Eight months of someone else’s work read in two days — before a line of code was written.
Fix or rewrite
The team says rewrite. The contractor says fix.
Arguments in two currencies — technical risk and FTE. You decide, knowing the price of both doors.
Finishing it cost more than removing eighty percent and going live in two weeks.
Technical due diligence
You are buying a business. You are buying its code with it.
What you are actually buying, and what the first year of owning it costs.
Change
Project rescue
The date has been given three times. The first two have passed.
One end-to-end path to production, and a date that holds. This is software crisis management, not extra hands.
The demo had been slipping for weeks. Fourteen days later the first machine was working on the street.
Modernizing a running system
There is a part of the system nobody wants to open.
The system changes with near-zero downtime — legacy modernization services in small steps, each with a backup plan.
Fifty-odd applications and five people for all of them: more than sixty percent moved in small steps.
System integration
It broke on their side, and it is our fault.
A seam that holds — and on which you can see whose side gave way. System integration consulting where hardware and state platforms meet.
The machine, the payment, the state reporting and the warehouse all have to reconcile, while the courier drives where there is no signal.
Design and build
Software architecture
A few decisions will be very expensive to undo later.
Decisions made and written down so the next hire can read them. Software architecture consulting with the code, not beside it.
One or two objects that had swallowed half the system came apart into thirteen separate parts — with production running.
Building to production
What arrived was a presentation and a document. The working system did not.
A working system, not a project about one. Custom software development services, from the business conversation to production.
Started from an empty repository; four years later people lay out shelves by it every morning.
Ownership
Fractional CTO
The developers say one thing, the business hears another.
One technical decision instead of two retellings. A fractional CTO or interim CTO who also writes the code.
Four years of answering for the result and for a team of four.
An engineering standard for the team
The team is always busy and nothing ships.
Moving between your own systems stops costing a day.
Five engineers hold fifty applications, and the incident profile stays quiet.
A separate way in
Situation not listed? Describe it in your own words. A first conversation needs two things: what is expensive to touch, and one number you can measure.
[email protected]