For consultancies, agencies, systems integrators and specialist firms
The senior architecture layer.
Without competing for your delivery.
Bring us in for one client problem: a difficult discovery, the architecture behind a proposal, an independent assessment, a readiness check, a handover check, or oversight while your team builds. You keep the build and the client.
How we work with partners
Three ways
to work with us.
Pick the one that fits the client and the project.
Subcontracted
We work for you, and you face the client.
Under your brand
We work as part of your team. We won't present the result to your client as an independent opinion.
Jointly
We're named alongside you, with roles agreed with the client.
In every model, the report says who asked for it and who paid. We call our work independent only when it is. We agree who can rely on the report before we start.
Example: an agency about to propose a rebuild asks us to review the client's system first. The proposal keeps what works, and the client sees a view from outside the agency, with the report saying who paid for it.
A first step for partners
Peer Review
for your proposal.
A written architecture view of the client's system or your proposed design, under your brand or jointly. It is paid and time-boxed, with the timing agreed up front, so it fits your proposal deadline.
We won't bid for delivery work at a client you introduced.
Commercial models: you resell our work at your rate, you refer the client and we contract directly, or we contract jointly. Terms are agreed per engagement.
Architecture Peer ReviewClear accountabilities
One engagement.
Explicit responsibilities.
Each engagement sets its own scope and decision rights, so our work fits with the teams already responsible for the system.
Sparkling
A named senior architect leads the contracted work, integrates specialist input and stands behind the recommendation.
Client leadership
The client makes the business, investment and acceptance decisions, and gives the access, context and time with the people who know the system.
Delivery teams
You and your partners build, test and run the system. Through Architecture Governance, we can review significant technical choices within the decision rights and hours we agree.
What we agree before we start
- The decision, the system boundary and the deliverables.
- The named senior architect, any specialists, available capacity and start date.
- Who hires us and pays; who receives the report and can rely on it.
- Client-facing roles, implementation ownership, and decision and escalation rights.
- Access, confidentiality, any earlier work we did on the system, and how our independence is described.
- Commercial terms for the scope of the engagement, and the intended handoff.
What does your client or delivery team need?
Tell us about the client problem and how you'd like to work together. 25 minutes on Teams, no preparation needed.