Engagements

Short. Written. Bounded.

Rubric engagements are deliberately structured for organisations that need senior judgement quickly and honestly. Same shape on every engagement: a clear scope, a written recommendation, a defined handover.

The work

Senior judgement on specific technology calls.

Rubric takes on short, bounded engagements where an organisation needs an experienced perspective on a call that would be costly to get wrong. Data platform selection. Cloud and infrastructure cost reviews. AI implementation guidance for small teams. Technology due diligence. Right-sizing infrastructure that has quietly outgrown its need.

The work is diagnostic and prescriptive. Interviews with the engineers doing the work, time inside the tooling, the data, the bills, the runtime metrics and the stack as it actually runs. Then a written assessment with concrete recommendations you can act on. Judgement, direction, and a clear read on what to do next.

How engagements work

Four steps, in order, on every engagement.

The shape is deliberate. You know what to expect from the first call to the handover.

Step 01

Scope

A short discovery conversation, always with the advisor directly. Agreement on the specific question, the shape of the deliverable and the fee before any billable work begins.

Step 02 · Weeks 1 to 3

Read

Interviews with the engineers doing the work, not only the ones presenting it. Time inside the tooling, the data, the bills, the runtime metrics and the stack as it actually runs.

Step 03 · Week 3 to 4

Written assessment

A short document, in plain English. What we think is really going on. What to do, what to stop, what order to do it in. Named risks, named trade-offs, quantified where the numbers matter.

Step 04 · After delivery

Handover

Your team executes. We stay available for a defined window to answer questions and pressure-test decisions as you act on the recommendations.

Working together

The practical arrangements, said plainly.

References and background on the first call.

Every engagement starts with a direct conversation. In that call, we walk through relevant prior work at whatever level of detail you would find useful, and we can arrange references from senior operators who have engaged the practice on similar questions. Trust is built before the engagement letter, not after.

Remote by default. On-site when the work earns it.

Most of a written assessment gets produced remotely, with video interviews and shared access to systems and dashboards. When on-site time is genuinely useful, whether that is a two-day working session with the engineering leadership, an executive presentation, or a portfolio-company visit, we do it. On-site work carries actual travel, lodging and per-diem expenses at cost, agreed in advance and separate from the engagement fee.

Our hardware, or yours.

Rubric works from a hardened, encrypted laptop as standard. For engagements where your security posture requires it, whether that is a regulated industry, a PE portfolio company with SOC 2 obligations, or an organisation with strict device-management policies, we work on client-provided and client-managed hardware for the duration of the engagement. The choice is yours.

Full-time on the engagement, or a few hours a week.

The default cadence for a two-to-four-week written assessment is a full-time focus by Rubric on the work. For longer advisory relationships, fractional CTO seats, or an ongoing second-read arrangement, we scope to whatever cadence the situation actually needs. Some months are a standing weekly call. Some are two days on-site and nothing in between. The engagement letter names the shape.

Who this is for

Small enough to move fast. Serious enough to want a considered read.

i.
Founders & CTOs

Growing companies of 20 to 150 people.

Real product, real customers, a technology call on the table that the internal team is close to but has no one senior enough to sign off on with confidence. A fractional CTO conversation without the retainer commitment.

ii.
Small engineering teams

Two to eight competent engineers, no twenty-year veteran.

The team is capable but nobody in the seat has taken decisions of this scale before. A written point of view from someone who has been through this before is worth more than another two junior hires.

iii.
Non-profit leaders

Executive Directors of mid-sized non-profits.

Real technology budgets, real growth pressure, no senior technical advisor on the roster. Often facing decisions like a data warehouse, a cloud migration, an AI programme or a platform consolidation. Wary of being over-sold by vendors.

iv.
PE operators

Operating partners at small private equity portfolios.

Portfolio companies needing technology due diligence, a post-close read on the platform, or a targeted cost review that a senior operator can turn around in weeks, not months.

Connect

Have a specific call on the table?

A short note is enough to begin. The first conversation is with the advisor directly, at no cost.