How we work
Engagement models
We prefer to commit to outcomes where the scope is clear enough to stand behind. Where it is not, we say so and structure the work to find out, rather than pricing a guess.
A defined outcome, delivered.
Discovery, architecture, implementation, and handover for a system you need built, modernized, or integrated - from a single platform component to a complete software product.
Fixed price or milestone-based where the scope is clear; a paid discovery phase first, or time-and-materials, where it is not.
Engineering capacity with technical leadership.
Specialist engineers, a small team, or architecture and technical leadership, working inside your project - directly for you, or behind a consultancy or integrator that owns the client relationship.
Time-and-materials or dedicated capacity, with Northkeep technical oversight. Defined work packages can be fixed price.
The system kept healthy after launch.
Business-hours maintenance, improvements, troubleshooting, software enhancements, and architecture guidance for systems already in production - ours or someone else's.
Scoped to an agreed capacity. Not a 24/7 operations desk, and no response guarantees beyond what the agreement sets out.
Working for a consultancy or integrator? The same models run behind your client relationship - see engineering partnerships. Need the system kept healthy after launch? See ongoing engineering.
How a project runs
Larger projects are phase-gated, so nobody commits to a number before the evidence exists to justify it. Your engineers can be embedded from the first phase rather than trained at the end.
The problem, the constraints, the current state, and what done looks like. Short and paid where the scope is genuinely unclear; folded into the proposal where it is not.
A target design with the trade-offs written down and the decisions defensible to your board and your own engineers - and a delivery plan priced on it.
Phased delivery against agreed milestones and acceptance criteria, with working software and infrastructure early and often rather than at the end.
Run responsibility moves to your team against documented decisions and runbooks - or stays with us as ongoing engineering, if that is what you want.
Who does the work
Every engagement has a named technical lead, accountable for scope, quality, and delivery. The engineering is done by engineers we employ or engage directly - including vetted subcontractors - working to our standards and under our technical oversight, with senior architectural review on what ships.
Today, Northkeep's founder is directly involved in the architecture and technical oversight of our engagements. As the company grows, that responsibility is shared with further technical leads - it is not dropped.
Principles
Start a conversation
We will come back with how we would approach it, which engagement model fits, and what we would need from you.