Strategy and advisory firms produce excellent data remediation plans and then hand them to a client who has to find someone to execute. Fortis is the engineering capacity behind the recommendation, under your name or ours.
Start a conversationThe gap is structural, not a criticism. An assessment practice and a delivery practice need different people, different utilisation models and different risk appetites. Firms that are excellent at one are rarely staffed for the other, and hiring database engineers to service occasional remediation work is a poor use of a balance sheet.
That is the whole basis for this. You keep the client relationship and the strategic work. We do the engineering the plan calls for.
If any of these describe your practice, there is probably something here worth a conversation.
You score a client environment, find lineage gaps, quality problems and governance holes, and produce a prioritised remediation plan. The client asks who does the remediation. Right now the honest answer is somebody else.
You can write the control narrative and design the framework. Implementing access control, encryption posture and audit logging in the database layer is a different discipline and you would rather not staff for it.
You hold the contract and need database depth on a workstream that does not justify a permanent hire. Cleared where the program requires it, and comfortable inside an accreditation boundary.
Strong on infrastructure, application and DevOps, thinner on the database layer underneath. The migration is going well until the data has to move without loss.
You build the product. Performance is degrading, the schema has outgrown its original design, or a client is asking questions about data handling that you would rather answer with a specialist in the room.
You are advising a client through a data problem and need hands to implement, without introducing a firm that will try to own the relationship.
No partner tiers, no certification requirements, no minimum volume. Pick whichever suits the client relationship.
We work as part of your delivery team. Your client relationship, your project management, your name on the deliverable. We are on the calls if that helps and invisible if it does not. Contracted through you, invoiced to you. We do not approach your client independently, during or after the engagement.
We appear as the database engineering specialist on the team, which some clients prefer and which some procurement processes require. This is the usual route for prime contractors and government delivery teams. Useful where clearance, regulated-environment experience or platform depth is being evaluated as part of the bid.
Federal capability and registrationDeliberately short. Most of these conversations resolve in under two weeks.
What the plan calls for, what the constraints are, and whether this is genuinely a database engineering problem. If it is not, we will tell you.
Deliverables, duration, access requirements and data handling in writing before anything starts. Time and materials where scope genuinely cannot be fixed, at a published rate rather than a negotiated one.
Mutual non-disclosure, non-solicitation of your client, and a teaming or subcontract agreement. Business associate agreement where health information is involved. Insurance certificate naming you as additional insured.
The people who scope the work are the people who deliver it. No account manager, no handover to a delivery team, no rotating staff. Senior technical leadership stays accountable from scoping through delivery, and you keep direct access to the engineers responsible for the architecture.
Send the scope, or just describe the problem. We will tell you whether it is work we should be doing, and what it would take.