Services
Senior engineering, without the agency layer
You talk to the person doing the work. That is the whole model — it is faster, it is cheaper than a bench, and nothing gets lost in the handoff between a salesperson and a delivery team.
Practice areas
Platform engineering
Multi-tenant application architecture on TypeScript, PostgreSQL, and Azure. Tenant isolation, RBAC, and audit designed in from the schema up rather than retrofitted after the first customer.
Enterprise migration
End-user computing and workload migration — discovery, dependency mapping, wave planning, and cutover. Delivered on real estates, not reference architectures.
Microsoft 365 & Entra ID
Tenant architecture, conditional access, identity governance, mail authentication (SPF, DKIM, DMARC), and break-glass design for organisations that have outgrown default settings.
Applied AI
Model routing, retrieval, and tool governance for teams that need AI in a production path with auditability — not a demo.
How we work
Four stages, each with an exit
You can stop after any stage and keep everything produced up to that point. Engagements that need a signature to escape are badly designed.
- 01
Assessment
A fixed-scope look at the current state and the constraints that actually bind. Ends in a written recommendation you own, whether or not you continue.
- 02
Design
Architecture and decision records before implementation. Every significant choice gets written down with its alternatives and consequences, so the reasoning survives the engagement.
- 03
Build
Implementation in defined increments against agreed acceptance criteria. Working software at the end of each, not a status report.
- 04
Handover
Documentation, runbooks, and a working environment your team can operate. No dependency engineered into the deliverable.
Is this a fit?
Good fit
- You need one senior engineer who owns the outcome end to end.
- The problem is architectural, and getting it wrong is expensive.
- You want the reasoning documented, not just the result.
- You are migrating something large and cannot afford a bad cutover.
Poor fit
- You need a team of ten starting Monday.
- You need 24/7 staffed support coverage.
- The work is outside the four practice areas above.
- You want a vendor who will not tell you when you are wrong.
If it is a poor fit, we will say so on the first call. info@celvextech.com