Delivery organization
45+ across six disciplines.
More than forty five people sit across planning, architecture, design, data, engineering, deployment and support. Planning and architecture lead each engagement. Engineering builds against their work. An engagement is staffed to its own shape rather than handed to whoever happens to be free.
The firm
Delivery organization
45+ across six disciplines.
Coverage
Programs nationwide, United States.
Engagement lead
Named, from discovery to deployment.
Commercial model
One number against a written scope.
How it is put together
The shape matters commercially. Work that is designed by the people who will build it tends to be designed around what is convenient to build. The disciplines below are in house, and they lead the work.
Planning
Learns the operation, writes the scope, and owns the baseline the result is measured against.
Solution architecture
Takes the decisions that cannot be reversed later and records each one with its reason.
Design
Owns every screen, every label and every word of help text, at phone width and desktop width together.
Data and analysis
Owns the model, the migration from whatever exists today, and the reporting that comes off it.
Deployment and support
Installation, the update path, documentation and the ongoing relationship.
Contracted to scope. Software engineering. Engineers are contracted against an approved scope and an approved design, which is a deliberate commercial choice rather than a gap.
It means capacity scales to the program in front of us instead of the program being cut to fit a fixed bench. It means the specification exists in writing before anyone is paid to build against it. And it keeps architecture independent of who is available, which is the single most common way a custom system ends up shaped by its supplier's staffing rather than by the client's work.
The scope, the design, the decision record and the verification stay with the firm throughout, and they stay with you afterwards.
Disciplines
Planning
In house.
Solution architecture
In house.
Design
In house.
Data and analysis
In house.
Software engineering
Contracted to scope.
Deployment and support
In house.
Every program has a named lead who is there from the first conversation to the last deployment. You are not handed to an account manager once the work starts, and the person who learned your operation does not disappear when the build begins.
Where an engagement touches a regulated or confidential environment, the people on it are the people named on the confidentiality agreement. Nothing is subcontracted onward without your knowledge.
Commercial model and ownership
Every project is quoted as a single number against a written scope. There is no rate card published anywhere, because the work is not interchangeable and a unit price would describe the wrong thing.
Program work is priced to the job
One number for that job, with payments tied to milestones, in the project budget's technology line.
Practice work is a fixed scope
At a fixed price, agreed before anything is built.
Changes are recorded as amendments
Priced, so a program never drifts quietly and you are never surprised by an invoice.
Not billed by the hour
An hourly engagement pays a supplier for being slow and hands the client every bit of the risk.
The point of commissioning custom software is that the organization ends up owning something, rather than renting a seat in somebody else's product. The documentation is written so a competent engineer can pick it up without us.
Your data, always
Exportable, in a documented structure.
The source
In your own repository where that is the agreement, and in escrow where a risk review requires it.
Documentation written for a stranger
Plain language, a route inventory and the decision record.
A system that can receive a fix
With a signed update path from the first release.
Programs nationwide, United States. To start: call (252) 666-7217 or email [email protected].