Inside co founder as a service, the complete guide for operators

Co founder as a service is a fixed term partnership where a senior technical team operates as your co-founder, builds the product, owns the architecture, and transfers full code and infrastructure ownership back to you on a published schedule. The relationship sits between hiring a fractional CTO for advisory bandwidth and committing 25% to 50% of the cap table to a permanent technical co-founder. This pillar is for operators considering co founder as a service in 2026: the studio house position, the engagement walkthrough, the rate benchmarks, the decision framework, the due diligence checks, and where every sibling article under the hub fits the picture.

Key takeaways:

• Co founder as a service typically combines a 5,000 to 25,000 dollar monthly retainer with 0.5% to 4% milestone vested equity, against 25% to 50% for a permanent co-founder (Carta Founder Ownership Report 2025).
• Solo founders are 23% more likely to fail than 2 to 3 person co-founder startups and take 3.6x longer to scale, per Y Combinator data covering 15 years of accelerator companies; a 12 to 18 month service engagement gives working evidence before a permanent commitment.
• The standard engagement runs 6 to 18 months across three phases (build, operate, transfer); the transfer ramp is published at signature, not negotiated at renewal.
• The studio house position: co founder as a service is the right move when you need senior technical judgement and shipping velocity, but you cannot defend a 25% to 50% cap table dilution before traction.
• Investor friendly engagements always carry a written IP assignment dated before any priced round and a named successor hire by month 12.

What is co founder as a service?

Co founder as a service (often abbreviated CaaS) is a contractual arrangement in which a senior technical team takes on the operational scope of a startup's technical co-founder for a fixed period, in exchange for a blended fee of cash plus a small equity grant. The team writes the production code, owns the cloud accounts, runs the engineering hiring loop, and reports to the founder the same way an in-house CTO would. The contract specifies the day, expressed as a milestone or a date, on which administrative ownership reverts to the founder.

Three contractual elements separate co founder as a service from neighbouring engagements. First, delivery accountability: the team is on the hook for shipping working software, not for delivering deliverables on a statement of work. Second, founder grade authority: the team commits architecture decisions and engineering hires the same way a co-founder would, inside a governance frame agreed at signature. Third, a transfer ramp: the engagement has a published exit, usually a documented handover of credentials, runbooks, and the engineering team to a new full time hire.

The model emerged from two parallel pressures. On one side, the technical talent supply gap has widened: 85% of companies report significant difficulty filling technical roles in 2025, up from 69% in 2022 (Korn Ferry survey reported by Tecla). The U.S. Bureau of Labor Statistics projects 317,700 annual openings in computer and information technology occupations through 2034. On the other side, founders who survived the 2022 to 2024 funding compression learned that committing 30% of the cap table to an unproven technical partner is a structurally expensive way to validate a thesis. Co founder as a service replaces that bet with a contractual relationship that can be measured, renewed, or ended.

The model now anchors several established programs. Antler runs a residency program structured around finding technical co-founders inside cohorts, with investment terms in the 100,000 to 190,000 dollar range for 10% to 12% equity in the resulting company; see the Antler residency program details for the program structure. Venture studios such as Atomic, eFounders and Founders Factory run a closely related variant in which the studio incubates the idea itself and brings in the operating founder later. Independent technical agencies and engineering collectives have built the third lane: they take the co-founder seat without sourcing the founder.

The studio house position on co founder as a service

La Boétie carries an opinionated position on co founder as a service, derived from operating across finance, insurance, legal, auction, eco transition and community verticals. The position is built on four commitments that we publish at every engagement signature, in plain language, and that diverge from how the field commonly treats the model.

Sovereignty by default. The studio refuses to build inside vendor locked stacks. The client owns the code, the cloud accounts, the deployment pipelines and the customer data from day one of the engagement. Étienne de La Boétie wrote in 1548 that voluntary servitude is a choice, and the modern equivalent is a startup whose entire product runs on a low code platform with an undocumented data export. Sovereignty is a non-negotiable: a service co-founder who leaves you locked into their tools is not a service co-founder, they are a sales channel. This rule rules out a meaningful share of the co founder as a service offers on the market.

Cash plus equity, with cash dominant before traction. The studio takes between 1% and 4% milestone vested equity in a typical engagement, paired with a monthly retainer that covers the team's loaded cost. Equity-only deals before product market fit produce two failure modes: the studio over-discounts effort against an illiquid asset, and the founder feels a 4% commitment evaporate when the company pivots. The published default is 70% cash, 30% equity, rebalanced as the company raises.

Opinionated redirection over order taking. The studio reserves the contractual right to disagree with a founder's brief and propose an alternative scope before signing. A founder asks for a no-code MVP rebuild; the studio assesses what is actually needed and proposes a four week production hardening of the existing prototype with a paid pilot attached. Order taking studios collect the invoice; opinionated studios protect the founder's runway. This is the Steve Jobs USP applied to engineering services: we build what you actually need, not what you asked for.

A published exit ramp at every renewal. The studio commits, in writing, to a named successor hire timeline by month 12 of any engagement that lasts longer. The transfer plan is not invented at the end; it is part of the original contract. Engagements that drift without a transfer ramp turn into permanent dependencies, which is a worse outcome than a slower internal build. The Boston Consulting Group's research on its corporate venture building approach reports a 66% success rate, against 20% to 30% for traditional venture capital (source); the studio reads that delta as a function of the transfer discipline, not the model's brand.

The house position disagrees with the field on one further point: co founder as a service is not a junior offering, and pricing it like one is a tell. A real engagement carries senior engineering judgement at the same daily rate as a fractional executive, which we cover in the rate benchmarks section below.

Service co founder versus contract CTO and full time co founder, scored

Founders who are weighing co founder as a service usually have two adjacent options on the table: a contract CTO (a senior engineer on a project statement of work) and a full time technical co-founder (a permanent partner with 25% to 50% equity). The three options solve overlapping problems differently. The table below scores each on the seven dimensions that determine the operating outcome.

For an operator with 12 months of runway and an unvalidated technical thesis, the framing is asymmetric. A contract CTO under-scopes the work: shipping a real product requires more than statement of work execution, and the moment the contract ends the founder owns the unfinished system without an engineering team. A full time co-founder over-commits: 30% equity is the most expensive form of validation a founder can write, and the cap table cannot be recovered if the partnership unwinds. Co founder as a service occupies the middle: enough delivery accountability to ship, enough equity alignment to stay engaged through the hard months, and a contractual end date that protects the cap table.

The trade-off inverts in two cases. When the company is the technical bet (a novel cryptographic primitive, a deep learning architecture, a hardware integration that requires hands-on iteration), the permanent co-founder relationship dominates because the technical decisions cannot be separated from the strategic ones. When the founder simply needs a senior advisor to sanity check an existing engineering team, a fractional CTO at 5 to 10 hours a week is a lighter and cheaper choice. The service co founder versus contract CTO scored side by side reference walks the dimensional comparison in finer detail, with a worked example for each operator profile.

Engagement walkthrough for a co founder as a service deal

A co founder as a service engagement runs in three phases mapped to the build operate transfer (BOT) industry standard adapted for early stage software. The phases are sequenced, not parallel, and each carries a defined exit gate that the founder signs off on before the next phase begins.

1. Build (30 to 90 days). The studio audits the existing assets, drafts the architecture for the first production release, sets up the cloud accounts, the deployment pipeline, the observability stack and the secrets manager in the founder's name from day one. A four to six person team is assembled around the engagement. The exit gate is a working deployed system with a non-empty test suite, an observability dashboard, and a documented architecture decision record. Founders frequently underestimate this phase; the industry standard for build operate transfer engagements runs 30 to 90 days for setup alone, with the operate phase typically extending 12 to 24 months according to the 2025 BOT model guide cited in the bibliography.

2. Operate (12 to 24 months). The studio runs engineering: weekly product sprints, hiring junior engineers as the company funds, integrating with downstream partners, responding to security incidents and shipping the roadmap the founder owns. The studio writes runbooks against every recurring operation. The exit gate is an operational set of three documents: a runbook library covering every production action, a hiring plan with at least one signed senior engineering offer, and a transfer rehearsal where the studio steps back for one week and the in-house team operates production unsupervised.

3. Transfer (60 to 90 days). Credentials rotate to the new hire. The studio shadows the in-house engineering lead for a documented period, then steps off the daily rota. The IP assignment, which was signed at the start of the engagement, is reconfirmed with a final inventory. The studio remains on a reduced advisory bandwidth, typically four hours per month for six months after transfer, to absorb the orphan questions that always emerge in week three of independent operation.

The published 6 to 18 month window covers most founder situations. Engagements at the short end (6 months) suit founders who are already raising a priced round and need a clean technical story by the data room close; the transfer happens against the new technical hire that the round funds. Engagements at the long end (18 months) suit founders who are pre-revenue and need a longer operate phase to find product market fit before the in-house team can credibly take over. The engagement walkthrough reference goes deeper on each phase, with the exit gate checklists and the artifacts the studio actually produces.

The critical contract clauses that hold across every engagement length are the IP assignment from day one, the published transfer date or milestone, the cash to equity ratio, the equity vesting schedule keyed to shipping milestones rather than calendar months, and the right of either party to terminate at the end of each phase with a defined wind-down period.

Service rate benchmarks for co founder as a service

The market for co founder as a service does not yet have a Carta-quality benchmark report. The table below combines fractional executive rate surveys, agency engagement comps and the studio's own engagement history to produce a defensible 2026 range for an operator in a major market (U.S., Western Europe, Israel). The numbers assume a four to six person engagement team led by a senior architect with co-founder grade authority.

The cash figures sit in line with fractional CTO surveys for 2025, which report monthly retainers of 5,000 to 25,000 USD and hourly rates of 200 to 500 USD (CTO.la 2025 pricing guide). Co founder as a service sits above the fractional CTO median because the engagement includes a full delivery team, not just senior advisory bandwidth. European day rates for fractional executives run from 600 to over 2,000 euros, anchoring the upper bound on the daily rate equivalent.

The equity figures align with the Carta 2024 data on fractional engagements: long term fractional CTO arrangements land at 0.5% to 2% equity, and dedicated service co-founders with delivery accountability climb to 2% to 4%. The cliff is the most negotiated clause: founders push for 6 months minimum, studios push for 0 with milestone vesting; the working compromise is 3 months with a defined first milestone (typically the build phase exit gate) as the cliff trigger.

Two cost surprises commonly catch founders. Cloud and tooling pass through: the studio invoices the cloud bill, the observability vendor, the analytics platform and the security tooling directly to the founder from day one, not as part of the retainer. Budget 1,500 to 6,000 USD per month depending on traffic. Hiring agency fees: when the studio sources the successor technical hire from its network, contracts usually include a placement fee of 15% to 25% of the first year salary, capped. Founders should ask for these line items at the proposal stage. The service rate benchmarks reference publishes a deeper tear-down of each line item with anonymised engagement comps. For a complete cost stack, the engagement cost breakdown reference is the line-by-line companion.

Three engagements where the playbook was load bearing

The studio's house playbook for co founder as a service has been load bearing in three engagements that span the operator persona spectrum. The cases below are summarised to protect commercial confidentiality, with the engagement shape and outcome made public.

Engagement 1: regulated finance product, France Épargne. A solo operator with a financial services distribution background and no engineering team needed to launch a regulated insurance distribution product against a six month regulatory window. The studio took the co founder as a service seat for 14 months: built the underwriting workflow, integrated with three insurance carriers, shipped the public site at france-epargne.fr, hired the first two engineers from the studio's network, and transferred operations to the new technical lead. Equity grant: 2.5%, milestone vested. Cash retainer: median band. Outcome: production traffic stable, three carrier integrations live, transfer completed on schedule.

Engagement 2: in-house SaaS spinout, Lynkflow. The studio incubated Lynkflow as an in-house insurance workflow tool, then spun it out as a standalone offering with a separate operating founder. The co founder as a service engagement covered the 9 month transition: documenting the architecture, separating the data, building the multi-tenant rails the standalone product needed, and onboarding the operating team. Equity grant retained inside the cap table at studio formation; no cash retainer (intra-group). Outcome: clean spinout with the operating founder owning day-to-day product decisions inside three months.

Engagement 3: vertical community platform, rubashkinshouse.com. A non-technical operator with a community-driven thesis needed a content and donation platform that could survive a 50x traffic spike during a single calendar event. The studio operated as service co-founder for 8 months: built the platform on a sovereignty-first stack (no platform lock-in), instrumented for the traffic peak, shipped the donation flow with a regulated payment provider, and trained the operator on the on-call rota for the event window. Equity grant: 1.5%, cliff vested at platform launch. Outcome: platform handled the peak event without an incident; the operator runs day-to-day operations independently.

The common thread across the three is the contractual frame: the founder owned the cap table going in, the studio shipped against a defined milestone schedule, the transfer happened on a published date, and the post-transfer advisory bandwidth was capped at four hours per month. The non technical founder field report reference covers the second and third profiles in operator-voice detail, and the edtech founder case study reference teardowns an engagement in the education vertical at the same level of specificity. The service relationship postmortem and service co founder anti-patterns catalog the failure modes from engagements that did not land cleanly, which is the more useful reading material if you are about to sign a contract.

Engagement scope decision framework for co founder as a service

Not every founder situation calls for co founder as a service. The decision rule the studio applies, refined over engagements across eight verticals, is reproduced below as a starting condition matrix. The rule gives an opinionated answer for each combination of runway, technical baseline and revenue stage.

1. Pre-product, less than 9 months of runway. Co founder as a service is the wrong scope. Either raise a longer runway or contract a fractional CTO for 8 hours a week to sanity check the founder's own DIY build. A 12 month engagement does not fit in 9 months of cash.
2. Pre-product, 12 to 24 months of runway, no engineering team. This is the sweet spot. A 12 to 18 month engagement covers build through operate and lines the founder up to either raise on shipped product or hire the permanent team after traction. Plan 25% of cash runway against the studio retainer; preserve 60% for the operate phase.
3. Pre-product, founder is a senior engineer. Co founder as a service is rarely the right fit. The founder is best served hiring a junior engineer pair and a fractional architect, or finding a co-founder in the founder's own network. Outsourcing the technical leadership the founder already has is a poor use of cash and equity.
4. Live product, paying customers, no in-house engineering depth. The engagement is a stabilisation play. Build phase compresses to 30 days (the system already exists), operate phase focuses on production hardening, security review, on-call rota and team hiring. Equity grant typically lower (0.5% to 2%) because risk is lower and the company has revenue.
5. Raising a priced round in the next 6 months. The engagement is a data room play. The studio cleans up the technical due diligence package, fills the architecture gaps the lead investor will ask about, and lines up the named successor hire that the new capital will fund. Engagements at the short end of the published window.
6. Post round, scaling engineering, founder is non technical. The studio runs engineering hiring, sits on the interview panel and trains the new VP Engineering for the first quarter, then transfers fully. Equity grant typically at the low end because the engagement is heavy on advisory and hiring, light on production code.

The matrix is opinionated by design. Studios that take every engagement at every starting condition are not optimising the founder's outcome; they are optimising their own bookings. The decision framework reference goes deeper on each row, with the diagnostic questions the studio asks before signing and the situations in which the studio actively recommends a competitor or no engagement at all.

Investor due diligence on service co founders

Investors who have priced more than a few rounds on companies with a service co-founder in the stack apply a consistent checklist during due diligence. The checklist is reproduced below in the form that operators will recognise from the data room request list of a sophisticated seed or Series A lead.

1. IP assignment dated before any priced round. The single highest priority document. An IP assignment dated after the term sheet creates a re-warranty obligation and can trigger a closing delay. Studios that resist signing this clause early are a red flag. Operators should sign at engagement start, not at funding close.
2. Named successor hire and transfer plan. Investors want to see who will run engineering after the studio steps off the rota, and on what date. A plan dated within six months of the funding event is reassuring; a vague "we will hire when the time is right" is a discount trigger of 10% to 30% on valuation according to the engagements the studio has observed.
3. Cash to equity disclosure in full. Hidden equity arrangements (off cap table side deals, future warrant grants tied to transfer milestones) are the most common cause of friction. The data room should contain the full engagement contract, not a summary. Investors run pattern matching against known studio templates; deviations attract scrutiny.
4. Equity vesting schedule continuing through transfer. A vesting schedule that fully accelerates on transfer aligns the studio with the founder during transfer; one that fully vests at engagement end aligns the studio with a quick disengagement. The healthy compromise is partial acceleration at transfer with the remainder vesting over the post-transfer advisory period.
5. Engineering hiring track record on file. Investors will ask for the names and start dates of the in-house engineers the studio has hired so far. A studio that hires consistently is much easier to underwrite than one that runs every engagement entirely with its own staff, because the latter is a single point of failure for transfer.
6. Production access audit. A short technical due diligence call where the studio walks the lead investor's technical advisor through the production system access controls. The single best signal of a sovereignty-first engagement is that the founder is already the root account holder on every cloud platform; if the studio has to grant access during the call, the engagement is structurally weaker than it should be.

Founders who walk into due diligence with these six items prepared close on faster terms and at the headline valuation the term sheet quoted. The investor due diligence reference is a deeper walkthrough with the exact document inventory and an annotated example data room.

What is changing in co founder as a service this year

Three structural shifts are reshaping the model through 2026, and operators who sign a 12 month engagement now should plan against each.

Shift 1: AI tooling collapses the build phase. Modern code generation tools, used responsibly inside an architected system, have compressed the 30 to 90 day build phase by 30% to 50% in the studio's own engagement history. The implication for pricing is that build phase setup fees are dropping, while operate phase retainers are holding steady because the operational scope (hiring, security, on-call, integrations) is not AI-displaceable. Korn Ferry research shows AI skill demand nearly doubled between 2024 (28%) and 2025 (51%) of job postings, with AI-related postings up 1,800% year on year in the U.S. (reported by Tecla). The studio's position is that AI compression is a discount founders should ask for at the build phase line item, not a justification for higher equity.

Shift 2: Sovereignty risk is now a board-level question. Founders who shipped DIY products on no-code or low-code platforms during 2023 to 2024 are now hitting the migration wall: the platform owns the data export, the customer relationships and the deployment surface. Co founder as a service engagements increasingly start with a 6 to 8 week extraction sprint from a previous DIY stack before the build phase even begins. The European market is leading this conversation; sovereignty conscious investors price it into term sheets.

Shift 3: Investor diligence on service arrangements has formalised. Two years ago, a service co-founder arrangement was a footnote in the data room. In 2026, lead investors run dedicated technical due diligence sessions on the studio relationship, with a standard question set covering IP, transfer, hiring and cash to equity disclosure. The shift is healthy: it filters out poorly structured engagements before they become later-stage cap table fights. Operators should expect the diligence and prepare for it from the start of the engagement, not at the term sheet close.

The sibling family on venture studio and equity for tech covers the broader market context for these shifts; the competitor service offer teardown maps how the field's largest competitors are responding to each.

FAQ: questions operators ask

What does co founder as a service actually mean?

Co founder as a service is a fixed term engagement where a senior technical team operates as your co-founder for a contracted period, building the product, owning the architecture, and transferring full code and IP back to you on a published schedule. Compensation usually combines a monthly retainer with a small equity grant (typically 0.5% to 4%) that vests against shipping milestones rather than calendar time. The relationship sits between a fractional CTO engagement and a permanent technical co-founder.

How much equity does a service co-founder take?

A service co-founder typically receives between 0.5% and 4% of fully diluted equity, well below the 25% to 50% a permanent technical co-founder commands. Carta's 2024 data shows fractional CTOs in long-term engagements land at 0.5% to 2%. Studios that lead engineering for the first 18 months often negotiate 2% to 4% with milestone vesting. The split reflects time-boxed commitment: the service co-founder leaves the cap table mostly intact for the next priced round.

How long does a typical co founder as a service engagement last?

Most engagements run 6 to 18 months, mapped to one of three end states: shipping a paid pilot, raising a priced seed round, or transferring the system to a full time engineering hire. The build operate transfer industry standard breaks this into a 30 to 90 day build phase, a 12 to 24 month operate phase, and a 60 to 90 day transfer phase. The studio publishes the exit ramp at signature, not at renewal.

Is co founder as a service the same as hiring a fractional CTO?

No. A fractional CTO advises on architecture, hiring, and roadmap for 5 to 20 hours a week, with no commitment to ship the product itself. A service co-founder owns delivery: they hold the keyboard, the GitHub admin, the AWS root account, and the engineering hiring loop. Fractional CTO rates run 5,000 to 25,000 dollars per month for advisory bandwidth. Co founder as a service includes the same advisory plus a full delivery team.

What happens to the code and the IP when the engagement ends?

Under a properly drafted co founder as a service contract, the founder owns the code, the IP, the infrastructure accounts, the customer data, and the deployment pipelines from day one. The transfer phase is a documented handover: credentials rotated, the engineering team trained, runbooks signed off, and source control transferred. Engagements that skip a written IP assignment leave the founder exposed during the next funding round.

When should a founder choose co founder as a service over a permanent co-founder?

Choose co founder as a service when you need shipping velocity now but cannot defend a 25% to 50% cap table dilution to investors, or when you have not yet validated the technical co-founder fit and need 12 months of working evidence before committing. Choose a permanent co-founder when the technical bet is the company itself (deep tech, novel algorithm, hardware) and you have already worked with the person for at least 6 months on a shipped prototype.

Will investors accept a startup whose engineering is run by a service co-founder?

Yes, when the engagement is documented and time-bounded. Investors look for three signals during due diligence: a signed IP assignment dated before the funding round, a clear transfer plan with named successor hire, and a vesting schedule for the service co-founder that aligns incentives through transfer. Engagements with hidden equity arrangements or undisclosed dependencies on the service team trigger valuation discounts of 10% to 30%.

How La Boétie runs these engagements

La Boétie operates a single flexible team of five to six engineers across European and Middle Eastern timezones, organised to take on co founder as a service engagements from the build phase through transfer. The team has shipped production systems across regulated finance, insurance distribution, legal tech, auction marketplaces, community platforms and eco transition. The engagement structure carries three publicly committed elements.

Architecture and delivery. The studio takes the architectural lead from day one: cloud accounts in the founder's name, repository structure, deployment pipeline, observability stack, and the first production release inside the build phase exit gate. The team writes the runbooks alongside the code, not after the fact. Recent engagements have shipped across france-epargne.fr, assurecompare.fr, llb-auction.com, assuied-avocat.fr, todopsy.fr, vertena.fr, rubashkinshouse.com, ganeden.xyz, nudjlabs.com and taamtaam.com, with platform tooling drawn from the studio's in-house SaaS portfolio (Cortex, Lynkflow, Amorphous, Socialforge) where it accelerates the founder's roadmap.

Sovereignty and ownership. Every engagement starts with the IP assignment signed, the cloud root accounts in the founder's name, and a written commitment that no production system will run on a vendor whose data export the founder does not control. The studio's open source work, including Broker Claw, Havrouta, Skillslib and a new LLM tokenizer, signals the same posture at the team level.

Transfer and continuity. Every engagement carries a published transfer date or milestone, with a named successor hire path. The studio commits to a four hour per month advisory bandwidth for six months after transfer, included in the engagement, to absorb the orphan questions that emerge in independent operation.

If you are weighing co founder as a service for your next 12 to 18 months, the next step is a studio intro call. Bring your current state (runway, team, product, customers) and the engagement question you want to answer; the call is the diagnostic the studio runs before quoting an engagement.

Conclusion

Co founder as a service is the right move for operators who need senior technical judgement and delivery velocity now, but who cannot or should not commit 25% to 50% of the cap table to a permanent technical partner before the company has earned that bet. The model trades a longer commitment for a published transfer ramp, and a permanent equity dilution for a small milestone vested grant paired with a cash retainer. The studio house position covered in this pillar is that a well structured engagement gives the founder 12 to 18 months of working evidence on the technical relationship while protecting the cap table for the next priced round. Use the decision framework section above to pick the starting condition that matches your runway and team, then read the focal article under that condition. The wider hub maps every other entry on co founder as a service so an operator can drill into the specific contract clause, benchmark or case study that the engagement question turns on.

Sources

• Antler, Antler venture studio, 2025
• Antler Residency program details, Antler, 2025
• Founder Ownership Report 2025, Carta, 2025
• How startup co-founders split equity 2024, Carta, 2024
• Why Startups Fail: Top Reasons, CB Insights, 2024
• A Proven Model for Corporate Venturing, Boston Consulting Group, 2022
• Big Venture Studio Research, Global Startup Studio Network, 2024
• Tech Talent Shortage 2025, Tecla citing Korn Ferry, 2025
• Fractional CTO Cost 2025 Pricing Guide, CTO.la, 2025
• Computer and Information Technology Occupations, U.S. Bureau of Labor Statistics, 2025
• YC stance on solo founders, Zyner, 2025
• Build Operate Transfer Model 2025 Guide, BOT Model Guide, 2025

Related reading:

• Co founder as a service engagement walkthrough
• Service rate benchmarks reference
• Non technical founder field report
• Engagement scope decision framework
• Investor due diligence on service co founders
• Service co founder versus contract CTO side by side
• Edtech founder case study
• Service relationship postmortem
• Service co founder anti-patterns catalog
• Engagement cost breakdown reference