Skip to content
Comtau
Book a callBook a call

About Comtau

A technology leadership practice that also builds.

Comtau gives companies senior, CTO-level ownership of strategy, architecture, engineering and delivery - and runs its own engineering system to carry those decisions into working, verified software.

What
Senior technology leadership and architecture
For
Startups, SaaS companies, SMEs, investors and acquirers
Led by
A senior CTO or architect on every engagement
Builds with
Its own AI-assisted engineering system

The work

Four kinds of technology work

Companies come to Comtau when technology decisions start costing time, money or confidence. The work takes one of four shapes.

See how the services connect
Lead
Ongoing technology leadership that owns the decisions - part-time, remote, packaged, or full-time for a defined period.
Decide
Senior judgement on one decision, answered with a written, execution-ready recommendation.
Assess
Independent, fixed-scope assessments - architecture, technical debt, due diligence, AI readiness - with scored findings and a plan.
Design & build
Target architecture and documented decisions, including for AI systems, with architects who stay to support implementation.

Principles

How Comtau thinks about technology work

  1. 01

    Architecture first

    Nothing gets built on a decision nobody made on purpose.

    Significant decisions are written down with their context, options and consequences, and approved by a person before implementation depends on them. The record stays with the company.

  2. 02

    Senior ownership, not opinion

    An advisor gives opinions. A CTO answers for the outcome.

    Every engagement is led by a senior CTO or architect, with explicit areas of accountability agreed at the start. Decisions are made, written down and owned - not left as suggestions in a call.

  3. 03

    AI-assisted, human-controlled

    Speed from AI assistance, without handing it control.

    Comtau builds its own software with AI coding agents. Each unit of work is bounded, observable and stoppable; people own architecture changes, new dependencies and releases.

  4. 04

    Evidence, not status

    Progress is shown, not reported.

    When Comtau builds, each unit of work closes with the checks that were run, their results and an independent review. Whoever did the work does not sign it off.

  5. 05

    Context stays with the company

    A handover package, not a dependency.

    Decision records, plans and handoff notes are produced throughout the work, so your team - or the next leader - starts from what is written rather than from memory.

  6. 06

    A straight answer

    Including when the answer is not us.

    We tell you plainly whether Comtau is the right engagement - and if it is not, what to look for instead.

AI-assisted engineering

How we think about building with AI

AI coding agents make implementation faster. Left alone, they also produce code nobody fully owns: changes that drift past what was asked, checks weakened until they pass, context that disappears with the session.

Comtau’s answer is structural rather than a matter of care. The same discipline an architect applies to a system - boundaries, explicit decisions, independent verification - is applied to the work itself.

Read the internal build case

Position

In practice

AI implements. People decide, review and release.

Context
Comtau builds its own software with AI coding agents inside its own system for planning, running and verifying the work.
Position
Every unit of work states what it may change and the checks that prove it. Execution stops on a failed check, scope growth or a missing approval, and a person decides.
Consequence
The controls that make this safe are the same ones a production AI system needs - so AI architecture advice comes from operating practice, not from a vendor diagram.
Comtau’s position, written as a decision record

Operating model

Most leadership engagements end at advice.Comtau’s can continue into delivery.

The same leadership that makes a decision can take it into scoped, AI-assisted implementation and show the evidence that it works. Each stage hands a written output to the next, from assessment to handover.

  1. Assess
  2. Architect
  3. Decompose
  4. Execute
  5. Verify
  6. Hand over
How Comtau works

Proven and evolving

What runs today, and what we don’t claim yet

A company page is easy to inflate. This is the honest boundary.

Runs today

  • Decisions recorded and approved before build
  • Bounded units of work with declared scope and stop conditions
  • AI-assisted execution in observable sessions from a pinned starting point
  • Independent, read-only review and an evidence record per unit
  • Human approval of architecture changes, dependencies and releases
  • A handoff note closing every unit

Not claimed, or not published yet

Client case studies
Published only with client approval. Today the case library holds one internal build.
Leader profiles
Added once real profiles are ready - never placeholders.
Autonomous agents
Not claimed. Agents work one bounded unit at a time, under a person’s control.
A product for sale
The engineering system is how Comtau works, not something it sells.

Start with the situation, not the service

Tell us what is happening. We’ll help you work out which kind of technology leadership you need - and whether that is us.

Book a call

Direct conversation with a senior CTO/architect. We’ll review your situation and determine the useful next step.