FAQ
Frequently Asked Questions
Straight answers on fractional CTO services, engineering advisory, AI DNA, and how Arc&Delta works.
About Fractional CTO Services
What is a Fractional CTO?
A Fractional CTO is a senior technical executive who works with a company part-time, providing the same strategic and operational leadership as a full-time CTO at a fraction of the cost. Rather than filling a single seat, they typically work across multiple companies simultaneously, bringing broader pattern recognition from parallel engagements. For most Series A to B companies, a Fractional CTO covers the same remit as a full-time hire: architecture decisions, hiring strategy, team structure, delivery operating model, and technical roadmap.
What does a Fractional CTO actually do day-to-day?
The day-to-day work varies by engagement stage, but typically includes: leading weekly engineering leadership standups, reviewing and shaping the technical roadmap, advising on hiring and org design, identifying and resolving delivery bottlenecks, and designing the engineering operating model — intake, planning, retrospectives, and metrics. In an AI DNA engagement, it also includes designing and shipping automation workflows. The goal is always to build systems that work without the Fractional CTO present, not to create dependency.
How is a Fractional CTO different from a full-time CTO?
A Fractional CTO is part-time and engaged for a defined set of outcomes over a specific period rather than as a permanent hire. The main differences are cost (significantly lower), flexibility (engagements can expand or contract with the company needs), and breadth of exposure (a fractional leader has typically worked across many company stages and sectors). The tradeoff is depth of immersion — a full-time CTO is fully embedded; a fractional one is a high-leverage lever, not a full-time operator.
When should a startup consider a Fractional CTO?
Common triggers include: the founding team has a strong product person but no senior technical leader; the engineering team is growing past 5 to 8 people and delivery is becoming unpredictable; a fundraise or board requires evidence of technical rigour; or there is a specific challenge (delivery velocity, AI adoption, a scaling crisis) that requires senior expertise for 2 to 6 months. A Fractional CTO is not a substitute for a full-time CTO at scale — once you are past 30 to 40 engineers with sustained growth, you likely need a permanent hire.
How long does a Fractional CTO engagement typically last?
Most engagements run 3 to 9 months. Short engagements of 6 to 8 weeks work well for scoped outcomes like an engineering audit or a specific scaling challenge. Longer retainers are appropriate when the company needs ongoing strategic leadership through a growth phase. Arc&Delta typically structures engagements as monthly retainers with a minimum 3-month commitment, reviewed at each milestone.
About Arc&Delta's Services
What is an engineering operating model?
An engineering operating model is the management layer that connects business strategy to daily engineering delivery. It covers: how work gets into the engineering team (intake and prioritisation), how it gets planned (roadmap and cycle design), how it gets tracked and delivered (standup cadences, ownership, escalation paths), and how performance gets measured and improved (metrics, retrospectives, feedback loops). Most engineering teams that struggle with delivery have weak or missing operating model design — not a talent problem.
What does an engineering audit deliver?
The Arc&Delta engineering audit is a 2 to 4 week structured assessment covering delivery velocity, team structure and ownership, technical architecture health, process bottlenecks, and AI readiness. It produces a prioritised findings report with specific recommendations ranked by effort and impact, plus a 90-day improvement roadmap. Companies use it when a new leader joins, ahead of a fundraise, or when delivery has consistently underperformed expectations.
What is AI DNA, and how do you embed AI into engineering teams?
AI DNA is our approach to redesigning engineering workflows so AI agents and automation handle the repetitive, pattern-based work that currently consumes engineering time. This is not about replacing engineers — it is about removing the coordination overhead, status updates, ticket creation, documentation, and triage work that occupies 20 to 40 percent of engineering time at most organisations. Arc&Delta designs, builds, and ships these automations as part of every engagement — not just advisory.
What types of companies does Arc&Delta work with?
B2B SaaS and software companies, typically Series A to C, with engineering teams of 5 to 50 people. We work with clients globally — engagements are conducted remotely, so geography is not a constraint. Common archetypes: a technical founder who has outgrown their ability to also be the engineering leader; a non-technical founder who has hired an engineering team but lacks confidence in the technical direction; a growing SaaS company whose delivery velocity has plateaued despite headcount growth; or a professional services firm building a productised software offering.
What makes Arc&Delta different from other engineering consultancies?
Three things. First, Arc&Delta operates as an embedded partner rather than a deliverable-based consultant — the work is measured in outcomes (delivery performance, AI adoption, team capability), not documents produced. Second, every engagement is grounded in measurement: DORA metrics and DX Core 4 are used to baseline and track improvement, so progress is visible to the board as well as the team. Third, Arc&Delta builds AI-first from the start — automations and agents are part of every engagement design, not an add-on.
Delivery and Engagements
How is a Fractional CTO engagement priced?
Every engagement is scoped individually, based on the cadence of involvement and the outcomes you need. Arc&Delta engagements are structured as monthly retainers. The right framing for the cost is comparison to a full-time CTO hire, or to the cost of a single bad hire at that level — a well-scoped Fractional CTO engagement typically pays for itself within the first 30 to 60 days if it unblocks a delivery bottleneck or prevents a wrong hire. Request a strategy call and we'll give you a transparent picture of scope and cost for your situation.
How does an engagement typically start?
It starts with a discovery call to map your current team, delivery performance, and most pressing challenge. If there is a clear fit, we scope an initial engagement — either an engineering audit (if the problem is not yet well-defined) or a structured Fractional CTO retainer (if the mandate is clear). Arc&Delta does not run long proposal cycles. Most engagements go from first call to signed agreement within one to two weeks.
How do I know if I need an advisory engagement vs. a Fractional CTO?
An advisory engagement is the right fit when you have a capable engineering leader in place who needs a senior sounding board — someone to pressure-test decisions, provide an independent perspective on hard calls, and hold the team accountable to the roadmap. A Fractional CTO engagement is the right fit when there is a leadership gap — either no senior technical leader, or a leader who is not yet operating at the level the company needs. When unsure, start with the engineering audit: it scopes the problem before prescribing the solution.
Do you offer project-based engagements or only retainers?
The engineering audit is the one structured project-based engagement — 2 to 4 weeks, fixed scope, fixed price. All other Arc&Delta work runs on a monthly retainer. This is deliberate: operating model design, AI DNA engagements, and team scaling unfold over months, and point-in-time advice without ongoing accountability tends to go unimplemented.
AI and Engineering Leadership
Why is my engineering team missing deadlines even though they seem to work hard?
The most common cause is a missing or broken delivery operating model — not effort or talent. Specifically: unclear ownership (multiple people responsible means no one is accountable), planning that does not account for actual capacity, and no structured feedback loop that identifies when work is derailing before the deadline passes. Adding headcount makes this worse before it makes it better, because new engineers add communication overhead before they add throughput.
Why did hiring more engineers slow us down?
Past a certain size (typically 8 to 12 engineers), adding headcount without scaling the operating model reliably reduces delivery velocity. Each new engineer adds coordination cost — more meetings, more review cycles, more context-sharing. If the planning and ownership model does not scale, more people means more congestion, not more output. The fix is not fewer engineers — it is a delivery operating model designed for the team actual size.
What are DORA metrics and why do they matter?
DORA metrics are four measurements of software delivery performance: deployment frequency (how often you ship), lead time for changes (how long from commit to production), change failure rate (what proportion of releases cause incidents), and mean time to restore (how quickly you recover from incidents). Organisations that perform well on all four have significantly better business outcomes than low performers. Arc&Delta uses DORA metrics alongside DX Core 4 to baseline engineering teams at the start of every engagement and track improvement over time.
What is an MCP server and why does it matter for engineering teams?
MCP (Model Context Protocol) is a standard developed by Anthropic that lets AI models connect to live tools and data sources at query time, rather than being pre-trained on static documentation. For engineering teams, this means AI assistants can query your actual codebase, Jira board, Confluence documentation, or a proprietary internal system — and give answers that are source-cited and current. Arc&Delta has used MCP to make legacy codebases queryable, automate ticket creation, and build knowledge assistants any team member can use without specialist training.
How does Arc&Delta approach AI adoption without creating risk?
Every AI workflow Arc&Delta designs is built around three principles: verifiability (every output can be checked before it propagates downstream), reversibility (no automation runs unsupervised on irreversible actions), and compounding (the automation runs frequently enough to compound value). Automations that fail one of these tests get redesigned or dropped. This is why the highest-ROI AI implementations are usually invisible infrastructure — routing, triage, document generation — not headline AI features.
How do I get started with Arc&Delta?
The best starting point is a 30-minute strategy call — request one via the contact form at arcanddelta.com/contact. Come prepared with a brief on your current team size, what is not working, and what you would want to be different in six months. If there is a clear fit, we will outline an engagement scope within 48 hours. If it is not a fit, we will say so directly and point you toward the right resource.
Ready to talk?
Request a 30-minute strategy call and we will outline an engagement scope within 48 hours.
Request a Strategy Call