Measured 31× engineering leverage with Claude Code.
Installed in your team in six weeks.
If your board has asked what the company is getting from Claude Code and the honest answer is “faster autocomplete,” the tool is not the problem. The operating system around it is. We install one, and we measure it before and after.
Two-week assessment, $25,000. Six-week embed, $35,000. A one-year Fulcrum license included with either. One signature, no procurement cycle.
Aggregate execution factor: senior-engineer-equivalent hours per task, divided by agent session minutes, summed over 3,552 tasks logged since February 22, 2026 (median task 22.5×). Every row is published and recomputable at charlessieg.com/leverage. Measured on our own build, not promised for yours. Yours gets measured.
Two engagements. Both fixed price.
Fixed scope, fixed price, one signature. Both start within two weeks of it.
The Assessment
One team, one real backlog. We measure how your engineers and their agents actually work today, audit the repos for what agents need and do not find, and demonstrate the difference on one of your own tickets.
- A measured baseline: hours and agent minutes per task, on your work
- An agent-readiness audit of the repos: constraints, tests, gates, tooling
- One live ticket, done the AI-native way, in front of the team
- A written installation plan you can run yourselves, or with us
Charles’s time: up to 40 hours over the two weeks, about 8 of them live with your team.
Fulcrum included. A one-year license to install and use Fulcrum in your environment. After that, $1,199 per year, only if you choose to keep it.
Ask about the AssessmentThe Embed
One team of up to six engineers. Week one is the baseline. Weeks two through five install the operating system inside your repos, pairing on real tickets. Week six measures it and hands it over.
- Everything in the Assessment
- The constraint graph: nested guidance files that make agents behave like your best engineer
- Pre-commit gates, review loops, and agent workflows wired into your repos
- Tool integrations where they pay for themselves, and nowhere else
- Week-six measurement against week one, and a playbook your team owns
Charles’s time: up to 110 hours over the six weeks, about 38 of them live with your team.
The guarantee. The second half of the fee is invoiced only if the measured lift at week six is at least 3× your week-one baseline.
Fulcrum included. A one-year license to install and use Fulcrum in your environment. After that, $1,199 per year, only if you choose to keep it.
Ask about the EmbedWeek by week
Because the work has a shape.
The same weeks, every time, which is why it is fixed price.
- Week 1Baseline and audit.Your team works its normal backlog while every task is logged: the senior-hours it would take, the agent minutes it takes. In parallel, the agent-readiness audit of the repos: constraints, tests, gates, tooling, and what an agent needs and does not find.
- Week 2Demonstrate and plan.One live ticket from your backlog, done the AI-native way in front of the team. Then the written installation plan you can run yourselves or with us, and a readout with the sponsor: the baseline number, the audit findings, and what six weeks would change.
- Week 1Baseline.Your team works its normal backlog. Every task is logged: the senior-hours it would take, the agent minutes it did take. No process changes yet. This is the number everything is measured against.
- Week 2Constraints.The constraint graph goes in: nested guidance files that tell every agent session how this codebase is built, what it must never do, and what done means. One repo at a time, each proven on a real ticket with the engineer who owns it.
- Week 3Gates.Pre-commit gates that refuse untested code, and review loops that catch what the gates cannot. Nothing is installed that a ticket did not justify.
- Week 4Workflows.Agent workflows for the work your team actually does: the defect fix that ships with its regression test, the feature that ships with its tests, the review that reads the diff before you do. Paired on real tickets.
- Week 5Tooling.Tool integrations where they pay for themselves, and nowhere else. Fulcrum is installed in your environment, and by the end of the week the team is logging its own leverage.
- Week 6Measure and hand over.The same measurement as week one, on the same kind of work. You get the number, the playbook, and a team that already knows how to keep it moving.
What you hold at the end.
Every deliverable is an artifact in your repositories or your inbox.
None of them is a promise in a deck.
- 01Fulcrum, installedin your environment under the one-year license, with a key for every engineer.
- 02The baseline record.Two weeks of logged tasks and a written baseline report: the aggregate execution factor, the median task factor, coverage, and the per-project breakdown, plus the raw export.
- 03The agent-readiness audit.A per-repo scorecard of guidance files, tests and coverage, pre-commit gates, CI, tooling, secrets handling, and documentation, findings ranked, each with what an agent needs and does not find.
- 04The live-ticket demonstration.The merged pull request, the prompt transcript, and the recording if you allow one.
- 05The installation plan.Week by week, for your repos and your team, with one repo’s guidance file drafted as the sample. It is the Embed’s plan customized to you, and it is what you run yourselves if you stop here.
- 06The sponsor readout.A short written document, presented in the closing meeting.
- 07The constraint graphin every in-scope repo: nested guidance files, each proven on a merged ticket with the engineer who owns the repo.
- 08Gates and review loopswired into those repos: pre-commit gates that refuse untested code, a coverage floor, and a review step that reads the diff before a human does.
- 09Agent workflowsinstalled in your repos and documented: the defect fix that ships with its regression test, the feature that ships with its tests, the review before merge, the deploy verification.
- 10Tool integrationswhere they paid for themselves and nowhere else, each documented.
- 11A team logging its own leverageby week five, with the fatigue assessment on.
- 12The week-six measurementagainst week one, same method, same kind of work. It is the document that decides the second invoice.
- 13The playbook.An operating manual you own: how to write guidance, how to add a gate, how to log, how to read the number, how to onboard a new engineer.
- 14The handover workshop,and its recording.
How much of Charles you get.
Fixed price does not mean unbounded.
The cap is in the statement of work, and so is what we need from you.
Over two weeks. About 8 of them are live with your team; the rest are the audit, the plan, and the agents doing the build work under Charles’s supervision.
Over six weeks, roughly 18 hours a week. About 38 of them are live with your team: the weekly session, the pairing, the office hours, and the readouts.
By written change order, agreed before the hour is spent. Remote by default; an on-site day is priced separately.
- One team of up to six engineers, and up to four repositories
- Your repositories, your accounts, your model subscriptions
- Any cloud, language, or repository host
- Each paired engineer available at least four hours a week
- The sponsor available for thirty minutes a week
- Repository, CI, and container-host access within three business days of signature. The clock starts when it exists.
The rooms Charles leads.
Every meeting is on the calendar before week one.
Nothing else is asked of your engineers except the pairing.
- Kickoff60 minutes
Sponsor and engineering leads. Goals, access, the measurement contract, and what happens in the two weeks.
- How to log leverage45 minutes, whole team
The one class: estimating senior-engineer hours, what counts as a task, and the MCP server and CLI that capture it.
- Office hours45 minutes, twice a week
Drop-in while the team baselines.
- The live ticket2 hours, whole team, week two
One ticket from your backlog, done AI-native in front of everyone, questions throughout.
- Sponsor readout90 minutes, end of week two
The baseline number, the audit findings, the installation plan, and what six weeks would change.
Week one is the Assessment’s week one: the kickoff, the logging class, and office hours. Then:
- Sponsor check-in30 minutes, weekly
The number so far, what went in this week, what is blocked.
- The Monday session90 minutes, weeks two through five, whole team
A class on the week’s theme with a live demonstration: constraints, gates, workflows, tooling.
- Pairing60 to 90 minutes, two or three times a week
With the engineer who owns the repo being worked. This is where each guidance file is proven on a real ticket, and where the teaching actually happens.
- Office hours45 minutes, twice a week
Drop-in, all six weeks.
- Week sixabout 5 hours across the week
The measurement review, a 2-hour handover workshop, and the closing sponsor readout.
Pavilion, included.
A pavilion is a structure built for one occasion and handed over when it ends. Every engagement gets one: a private online workspace, set up in week one for your sponsor, your engineers, and us, holding everything the engagement produces and everything it needs from you.
The calendar of sessions. Every recording, with its transcript and a reviewed summary for the people who were not in the room. The audit, the plan, the readouts, and the playbook, each a version your sponsor accepts. The discussion around them. The decisions, with their reasons. The action items and the obligations on both sides. The measurement panel, wired to your Fulcrum. At the end, one archive of all of it, which is yours. Read about Pavilion.
- The calendar: every session, with its recording, transcript, and summary
- The documents: audit, plan, readouts, playbook, each version accepted by your sponsor
- The discussion, anchored to the thing being discussed
- The decisions log: what was decided, by whom, and why
- Action items and the obligations on both sides, week by week
- The measurement panel, wired to your Fulcrum installation
- The export: every document, transcript, decision, and recording, yours to keep
Pavilion is a product of Renkara Media Group, Inc., operated for the engagement and exported to you at its close.
The tools of the engagement.
Nothing exotic, and nothing you have to buy.
Everything the engagement produces is recorded, transcribed, and left with you.
Fulcrum
Installed in your environment under the included license. Every task the team logs, the baseline, and the week-six number live here, and the record stays yours.
Your repositories and CI
Guidance files, gates, workflows, and the playbook are committed to your repositories and run in your continuous-integration system. Nothing is hosted by us.
Claude Code
On your subscription, in your accounts. The live ticket, the pairing, and every workflow are run with the tool your engineers already have.
Zoom
Every session is held on Zoom and recorded with your permission. Zoom’s transcripts and recaps are delivered with each recording, so the people who were not in the room get the whole meeting, not a summary of it.
Pavilion
Set up for your engagement in week one. The calendar, every recording with its transcript and summary, the documents your sponsor accepts, the discussion, the decisions, the action items and obligations, and the measurement panel, in one place you keep afterward.
Scheduling, approvals, change orders, and invoices go by email, so the commercial record of the engagement is in your inbox, not in a portal you lose access to.
Fulcrum, included.
Fulcrum is the instrument behind the 31× number: a leverage record kept at the time of the work, not reconstructed afterward. Every task carries the senior-hours it would have taken and the agent minutes it did take, so the week-six number is measured with the same instrument as week one.
Both engagements install Fulcrum in your environment under a one-year license. After the first year, keep it for $1,199 per year, or do not. The record you built stays yours either way. Read about Fulcrum.
- Year one
- Included with either engagement
- Each year after
- $1,199 per year, if you choose to continue
- Where it runs
- Installed in your environment
- The record
- Yours, whether or not you renew
Who this is for
- A VP of Engineering, CTO, or head of platform with 30 to 3,000 engineers
- Already paying for Claude Code, Copilot, or Cursor, and not seeing it in throughput
- One team willing to work differently for six weeks and be measured doing it
- Budget authority for a fixed-price engagement without a procurement cycle
Who it is not for
- –Teams that want a tool recommendation. The tool is not the bottleneck.
- –Organizations that cannot let an outside engineer work inside their repos
- –Anyone who needs a slide deck more than a measured number
The receipts
Between February and August 2026, one engineer and Claude Code built and launched an adaptive learning platform. Everything below is measured, not estimated, and most of it is public.
The operating system behind those numbers is what gets installed: 57 nested guidance files that constrain every agent session, pre-commit gates that refuse untested code, a fleet of internal tools the agents operate, and a leverage record kept at the time of the work, not reconstructed afterward.
Read the thinking: The Leverage Factor, Defending the Numbers, and Agentic Coding and Decision Fatigue, republished on the blog from charlessieg.com.
Who does the work
Charles Sieg. Not a team that learned this from a course; the person who did the work above. Building software since 1997. Shipped AccelaStudy on the App Store’s opening day in 2008 and grew it to 30 million downloads across 300 published apps. Cloud architect and platform engineer for Fortune 1000 clients across healthcare, pharma, and financial services. Sole inventor on every patent in the portfolio. Both engagements are delivered by Charles personally, inside your repos, with your engineers.
Questions a VP asks first
Does our code leave our environment?+
No. The work happens in your repositories, your accounts, and your model subscriptions. Nothing is copied out, and nothing of ours is left behind that you do not own.
Who owns what gets built?+
You do. The guidance files, gates, workflows, and playbook are yours outright. We keep nothing but the measurement, with your name off it unless you say otherwise.
What does “31×” actually mean?+
For every task, we estimate the hours a senior engineer familiar with the codebase would need, and we record the agent session minutes it actually took. Summed over 3,552 tasks, the ratio is 31. The median task is 22.5×. It is an upper-tail record of one operator with full product authority and no handoffs, which is why your number gets measured rather than assumed.
Why fixed price?+
Because the work has the same shape every time and because hourly engagements go through procurement. A fixed-price sprint with a defined deliverable is a purchase a VP can make this week.
What if it does not work for our team?+
Then you pay half. The second half of the embed fee is invoiced only if week six measures at least 3× week one. You keep everything that was installed either way.
How much of Charles’s time do we actually get?+
Up to 40 hours in the Assessment and up to 110 in the Embed, with about 8 and 38 of those hours live with your team. The caps are written into the statement of work. Anything beyond them is a written change order at $450 per hour, agreed before the hour is spent.
Is there training, or is it all pairing?+
Both, and pairing does the heavier lifting. The Assessment has one class, forty-five minutes on how to log leverage. The Embed adds a ninety-minute session each week on that week’s theme, with a live demonstration, and two or three pairing sessions a week with the engineer who owns the repo. Every session is recorded for the people who could not be in the room, if you allow recording.
Do we need to be on AWS?+
No. The engagement is about how your engineers and their agents work. Cloud platform, language, and repository host do not change it, though AWS is where we have the deepest history.
Is Fulcrum a subscription?+
Not during the engagement. Both engagements include a one-year license to install and use Fulcrum in your environment. After that it is $1,199 per year, only if you choose to keep using it. There is nothing to cancel, and the leverage record you built stays yours.
Start with an email.
Tell us the team, the stack, and what your board asked. You will hear back from Charles within one business day, and the first call is thirty minutes.
Claude and Claude Code are trademarks of Anthropic, PBC. GitHub Copilot is a trademark of GitHub, Inc. Cursor is a trademark of Anysphere, Inc. Zoom is a trademark of Zoom Video Communications, Inc. Vantalect is not affiliated with or endorsed by any of them.