Skip to main content

Selected work

Technical transformation that increases enterprise value.

Bottega8 leads product, engineering, and AI transformation inside consequential companies—reducing structural cost, restoring execution, building production agent systems, and aligning product-market fit, positioning, GTM, and sales motion to the new technical advantage.

Principal-led across company economics, board decisions, product-market fit analysis, Agentic AI architecture, IP consolidation, and operating model. When production delivery is required, forward-deployed engineers work directly with client teams from technical scoping through build, evals, rollout, and internal ownership.

Selected outcomes

Business result first. Technical depth underneath.

Scan the economic or operating result. Open any engagement for the architecture, intervention sequence, agent and eval design, and measurement context.

Case 09

PE-backed healthcare AI

Board & Investor

Governed clinical agents in production

Two governed agents deployed into clinical production

Technical mechanism: Interim CTO leadership, principal AI engineering, Agentic AI architecture, agent harness, clinical deployment, evals, and trust controls

2 agents

Clinical deployment

governed agents deployed into clinical production

View case details

Business situation

A late-stage healthcare AI company had meaningful demand and proprietary clinical-workflow data, but fragmented architecture, uneven release discipline, vendor dependency, weak observability and evaluation, and unclear platform ownership constrained safe clinical deployment and created material scale and diligence risk.

The board, investors, and executive team needed to prove that agents could operate safely in live clinics, earn healthcare-system trust, and scale on an architecture the company could govern and own.

Business objective

Deploy governed agents into clinical production while converting proprietary data and workflow advantages into an investor-ready platform with durable operating control and internal ownership.

Two governed agents reached clinical production and earned healthcare-system trust. Under Bottega8’s interim CTO, principal AI engineering, and Agentic AI architecture leadership, the company also became auditable, investor-ready, and able to own the system as durable IP.

Intervention sequence

  1. 01 Bottega8 served as interim CTO and led principal AI engineering and Agentic AI architecture across the transformation.
  2. 02 Ran principal-level diligence across code, architecture, security, data, product, talent, vendors, delivery economics, and the operating model.
  3. 03 Translated the findings into board decisions, investment priorities, architecture sequencing, accountable owners, and an execution roadmap.
  4. 04 Built the vertically optimized agent harness and reference architecture around governed state, observability, evals, human controls, release discipline, replay, and auditability.
  5. 05 Deployed governed agent workflows into clinic production and established the evidence, escalation, and operating controls required for healthcare-system trust.
  6. 06 Established an engineering-health system, directed the vendor transition, clarified platform ownership, and defined the senior hiring plan required for durable internal control.
Technical system
  1. Independent diligence
  2. Board decisions
  3. Agent harness
  4. Evals + trust controls
  5. Clinic deployment
  6. Engineering health
  7. Vendor transition
  8. Platform ownership

The production agent system, clinical trust model, investment narrative, and ownership plan became one execution program.

Starting point

Meaningful demand and proprietary workflow data constrained by deployment, scale, and diligence risk

Intervention

Interim CTO leadership, principal AI engineering, Agentic AI architecture, agent harness, clinical deployment, evals, and trust controls

Measurement context

Documented production engagement, deployed Agentic AI in clinics across the US

Executive implication: Clinical agent systems earn institutional trust when production architecture, evals, evidence, human controls, board decisions, operating discipline, and permanent ownership reinforce one another.

Case 02

Regulated financial data

Board & Investor

Enterprise data economics reset

$4.2 million in annualized savings from a product, platform, and cost reset

Technical mechanism: Portfolio rationalization, vendor and cloud consolidation, platform refactoring, dependency reduction, and operating redesign

$4.2M

Realized economics

annualized savings from cloud, vendor, platform, and operating-cost reduction

View case details

Business situation

A late-stage financial-data company had trusted institutional data, defensible IP, and strong engineers. Fragmented product lines, acquired platforms, overlapping vendors, manual reconciliation, unclear ownership, and legacy cloud architecture were consuming capital and slowing production.

Leadership needed one evidence base connecting the assets worth protecting to the work that required consolidation, automation, restructuring, investment, or discontinuation.

Business objective

Release structural cost while protecting differentiated data assets, improving production economics, and creating a credible platform and AI modernization sequence.

The engagement released approximately $350,000 per month in structural cost, improved the platform investment model, and gave leadership a sequenced plan for consolidation, refactoring, automation, and ownership.

Intervention sequence

  1. 01 Connected product value, code, data architecture, cloud, vendors, IP, organization, customer workflow, COGS, and unit economics in one operating baseline.
  2. 02 Eliminated low-value work and exposed organizational cost overruns, duplicated ownership, and acquired systems that could not justify continued spend.
  3. 03 Consolidated vendors and external cloud services while defining a centralized API layer, modular pipelines, more real-time ingestion, and clear platform ownership.
  4. 04 Refactored critical platform paths and reduced third-party dependencies that impaired accuracy, reliability, and time to production.
  5. 05 Sequenced automation and agentic-AI opportunities across onboarding, reconciliation, anomaly detection, QA, support, query optimization, and FinOps.
Technical system
  1. Economic baseline
  2. Product + data value
  3. Vendor + cloud consolidation
  4. Platform refactoring
  5. Accuracy + production flow
  6. Realized savings

Cost reduction came from technical and operating redesign—not an indiscriminate infrastructure cut.

Starting point

Fragmented acquired platforms, overlapping vendors, legacy cloud spend, manual operations, and unclear ownership

Intervention

Portfolio rationalization, vendor and cloud consolidation, platform refactoring, dependency reduction, and operating redesign

Measurement context

Approximately $350,000 per month observed during the engagement

Executive implication: Enterprise data economics improve when product value, architecture, vendors, cloud, dependencies, organization, and customer workflow are treated as one technical operating system.

Case 10

Healthcare AI delivery

Product & Engineering

Governed agentic SDLC transformation

Approximately 2.5× sprint throughput in 12 weeks without changing the team

Technical mechanism: Governed coding-agent operating system across the complete SDLC with human architecture, security, merge, and release authority

≈2.5×

Measured delivery result

completed story points per sprint across six consecutive sprints

View case details

Business situation

A healthcare AI organization needed multiple clinic launches and new agent workflows from a constrained engineering team without increasing regression, PHI, security, or architectural risk.

The existing delivery system could not create the required throughput safely; accelerating code generation alone would have amplified review, integration, and release risk.

Business objective

Increase completed delivery with the same team while preserving human authority over architecture, security, merge decisions, PHI controls, and production release.

Completed story points per sprint increased approximately 2.5× across six sprints. Defect, first-draft implementation, and product-decomposition cycles also improved directionally without changing the team or transferring production authority to agents.

Intervention sequence

  1. 01 Established one governed delivery system spanning requirements, ADRs, decomposition, implementation, testing, review, staging, UAT, and release.
  2. 02 Built a coding-agent harness with repository context, bounded tools, isolated execution, repeatable task structure, and explicit review gates.
  3. 03 Kept architects and engineers accountable for system design, security, quality, merge decisions, and production authority.
  4. 04 Installed evals, regression evidence, observability, and release artifacts so throughput gains remained inspectable and governable.
  5. 05 Measured completed story points across six consecutive sprints using the same team and estimation convention.
Technical system
  1. Requirements
  2. ADRs + decomposition
  3. Coding-agent harness
  4. Implementation + tests
  5. Human review
  6. Staging + UAT
  7. Production authority
  8. Six-sprint measure

The 2.5× result came from redesigning the complete delivery system, not from replacing engineering judgment.

Starting point

Constrained engineering capacity facing multiple launches, new agent workflows, and regulated production risk

Intervention

Governed coding-agent operating system across the complete SDLC with human architecture, security, merge, and release authority

Measurement context

Measured using the same team and estimation convention; supporting cycle-time figures combine observation and estimates

Executive implication: Agentic engineering becomes durable operating leverage when the harness, context, task decomposition, evals, controls, review, and release system are designed together—and the throughput comparison is measured consistently.

Case 01

Investor-backed marketplace

Board & Investor

Board-appointed marketplace turnaround

A 10-week company reset that helped guide a failing business to exit within a quarter

Technical mechanism: Board-appointed Bottega8 operating as an integrated CTO, CPO, and CRO function across diagnosis, turnaround, relaunch, and exit guidance

Exit

Company outcome

within a quarter of a Bottega8-led company turnaround

View case details

Business situation

An investor-backed marketplace was approaching failure. Board-appointed Bottega8 ran technical and commercial forensics across the team, systems, process, IP, product-market fit, positioning, GTM, and sales motion, then took integrated operating leadership across technology, product, and revenue.

The board and executive team needed an immediate company truth: what customers still valued, what could be preserved, what had to change, and whether a credible operating and commercial recovery was possible.

Business objective

Protect the company’s differentiated assets, restore product and engineering execution, reposition the offer for enterprise demand, rebuild the GTM and sales motion, and create a credible path to an exit.

During an intensive 10-week Bottega8-led engagement, the company realigned its product, technology, operations, positioning, and sales motion, relaunched against market demand, and restored a viable operating trajectory. Bottega8 then helped guide the company to an exit within the following quarter.

Intervention sequence

  1. 01 Audited customer evidence, product-market fit, product viability, code, architecture, data, IP, team capability, process, operating economics, pipeline, and decision rights as one company system.
  2. 02 Presented the board with an integrated product, engineering, operations, and GTM plan with a sequenced decision and execution roadmap.
  3. 03 Operated as an integrated CTO, CPO, and CRO function during the reset, directing the executive team, product and engineering work, and commercial relaunch.
  4. 04 Repositioned the product for enterprise buyers, restructured the GTM and sales motion, and relaunched the company against validated demand.
  5. 05 Reset architecture, delivery controls, release discipline, ownership, and agent-driven engineering workflows while mentoring the existing team.
  6. 06 Installed the executive cadence, operating measures, and accountability required to sustain the turnaround beyond the engagement.
Technical system
  1. Company diagnosis
  2. Board appointment
  3. Integrated company plan
  4. CTO + CPO + CRO leadership
  5. Product + GTM repositioning
  6. Engineering + operating reset
  7. Market relaunch
  8. Exit within a quarter

The turnaround connected company truth, board decisions, product and technical leadership, commercial relaunch, and exit execution.

Starting point

Investor-backed marketplace approaching failure with product, technical, operating, positioning, and GTM risk

Intervention

Board-appointed Bottega8 operating as an integrated CTO, CPO, and CRO function across diagnosis, turnaround, relaunch, and exit guidance

Measurement context

Documented engagement; user confirmed the 10-week reset and exit timing

Executive implication: A board-appointed operator can change enterprise value when company forensics, product-market fit, technical direction, team leadership, positioning, GTM, and execution are treated as one turnaround system.

Case 03

Enterprise data platform

Product & Engineering

Enterprise data delivery reset

$2 million in savings—and a faster, more accurate path to production

Technical mechanism: Cost excavation, vendor consolidation, platform refactoring, dependency removal, and delivery redesign

$2M

Realized economics

in savings while revitalizing the company for its next institutional funding round

View case details

Business situation

A data company was carrying expensive third-party dependencies, duplicated vendor spend, organizational cost overruns, and brittle production paths that affected accuracy and release speed. Bottega8 traced the economics into the architecture and operating model, then directed the changes required to remove structural cost.

Leadership could see rising cost and slower delivery, but the financial symptoms were distributed across vendor contracts, code dependencies, data workflows, team boundaries, and production ownership.

Business objective

Reduce structural cost, remove critical third-party dependencies, improve data accuracy, and shorten the path from change to production without weakening the differentiated platform.

The company removed approximately $2 million in structural cost, improved technical control over data accuracy and release speed, revitalized the business, and entered its next institutional funding process from a stronger operating position.

Intervention sequence

  1. 01 Established a cost and dependency baseline across vendors, outside cloud services, data pipelines, production systems, and organizational ownership.
  2. 02 Eliminated low-value work and identified areas where unclear accountability had produced egregious cost overruns.
  3. 03 Consolidated overlapping vendors and external services while preserving the capabilities the platform genuinely required.
  4. 04 Refactored critical data and production paths to remove third-party dependencies, reduce failure modes, and improve accuracy.
  5. 05 Redesigned delivery ownership and release flow so validated changes reached production faster and with clearer operational accountability.
Technical system
  1. Cost + dependency baseline
  2. Vendor consolidation
  3. Platform refactoring
  4. Data accuracy controls
  5. Production flow redesign
  6. Realized savings

The savings came from removing structural complexity while improving technical control and production performance.

Starting point

Overlapping vendors, high external spend, brittle dependencies, organizational overruns, and slow production flow

Intervention

Cost excavation, vendor consolidation, platform refactoring, dependency removal, and delivery redesign

Measurement context

Realized engagement savings; company and reporting period generalized

Executive implication: The largest technical cost opportunities often sit across architecture, vendors, organization, and production flow; realizing them requires engineering and operating change together.

Case 06

Regulated enterprise workflows

Enterprise AI & Agents

AI document review

Complex enterprise document review reduced from 1–2 weeks to minutes

Technical mechanism: Multimodal agent harness, domain tools, provenance, eval suites, replay, observability, and human review

7–14×

Workflow acceleration

faster complex document review with human-in-the-loop control

View case details

Business situation

Document-heavy enterprise workflows lose essential meaning when PDFs, spreadsheets, presentations, contracts, tables, graphs, and supporting records are reduced to generic text chunks.

A plausible answer was insufficient: every conclusion needed to preserve page context, evidence, domain structure, and the ability to replay and challenge the decision.

Business objective

Build a production AI and machine-learning system that reduces complex document review from weeks to minutes without separating an answer from its evidence or accountable reviewer.

One to two weeks of elapsed review across stakeholders became minutes of AI analysis with human-in-the-loop control. End-to-end workflow throughput improved an estimated 7–14×, depending on corpus size and workflow.

Intervention sequence

  1. 01 Built a multimodal agent harness for page-level text, table, graph, clause, image, and relationship analysis.
  2. 02 Defined parsing, retrieval, comparison, citation, and workflow tools around domain semantics rather than generic chunks.
  3. 03 Preserved provenance, versioning, evidence links, context boundaries, and traceability through workflow action.
  4. 04 Installed golden, adversarial, and regression evals for extraction, citation fidelity, reasoning, and model changes.
  5. 05 Kept replay, observability, exception handling, and accountable human review inside the production decision path.
Technical system
  1. Page analysis
  2. Domain structure
  3. Evidence links
  4. Workflow action
  5. Human review
  6. Replay record

The answer, evidence, human decision, and replay record stay in one governed loop.

Starting point

One to two weeks of review across multiple stakeholders

Intervention

Multimodal agent harness, domain tools, provenance, eval suites, replay, observability, and human review

Measurement context

Directional workflow estimate; realized time varies with document-corpus size and customer workflow

Executive implication: The production advantage is the harness around the model: domain tools, context control, evals, evidence fidelity, replay, observability, and accountable review.

How the work gets done

Principal-led transformation. Forward-deployed engineering.

Principal-level operators set the business objective, technical direction, economics, governance, and accountability. Forward-deployed engineers work directly with client product, domain, data, and engineering teams to scope, build, integrate, evaluate, and launch production systems in the client’s real operating environment. Field learning informs the architecture, product roadmap, controls, and operating model; internal teams leave with working systems and the authority to carry them forward.

Open the technical operating model

Agent systems

Agent harness design, tool contracts, context boundaries, orchestration, golden and adversarial evals, human approval gates, replay, observability, security, and controlled release.

Product and platform

Product architecture, data pipelines, multimodal workflows, refactoring, dependency removal, platform consolidation, production reliability, and time-to-production improvement.

Company transformation

Company economics, product-market fit, positioning, GTM, technology and IP strategy, organization design, decision rights, interim leadership, board reporting, and permanent ownership.

Next decision

Bring us the economic problem and the technical constraint.

In the first conversation, we will test the value pool, the execution risk, and the first decision required. If we are not the right team, we will say so.

Get started