Project · Active · Phase 3, Build v1

Digital workforce as a company's operating team

Started Last entry Owner Simon Edwards

Dashboard

Articles
1
ADRs
2
Cost to date
£45.00
Skills promoted
6

Phase 3 of 6: Build v1

  1. Spark
  2. Define
  3. Build v1 (current)
  4. Converse
  5. Harden
  6. Retro

Purpose. Blankitt is a founder-led UK platform of AI, IT, security and business tools, built by EAS Technology Consulting. The founder is also the engineer, so everything between “engineer” and “company owner” is unstaffed: product management, security review, release engineering, marketing, sales and the weekly reckoning. Blankitt is a retail business whose products happen to be digital, so the operating team’s job includes the shopfront, the checkout and the campaigns, not just the engineering. This project builds that middle layer as a set of role agents in Claude Code, committed to the company’s own repository, and records what they get right, what they get wrong and what they cost.

Hypothesis. Six role agents under one founder can run the operating team of a founder-led software company, and the Monday status page will show which of them earned their keep.

Where it is. Phase three of six, building the first version. The six roles exist and have each done their first job: a security review that found and fixed a real hole, a release check, a backlog, a brand audit, an outbound draft, and the first Monday status page. The phase ends when a week can pass with the founder acting on what the roles produce, rather than prompting them to produce it. After that comes the phase where the roles work alongside the founder day to day, then hardening, then a retrospective.

Start here. The first field note, the first ADR, and the Chief of Staff role card.

Tools in use. The security reviewer, release check and the rules they follow are published as an open-source pack, security-skills, in the same shape as Matt Pocock’s skills so the same installers work. The pack is the role card with the company facts taken out; ADR 2 records why.

How this differs from the enterprise project. The enterprise project asks how much of one security leader’s job a digital workforce can do inside a large Microsoft estate. This one asks how much of a whole company’s operating team it can be, with the founder as the only human. Same question, opposite end of the scale, different stack.

The team

Start here

  1. The question that found two doors

    Two holes in two days, in a product that sells email security and in the oldest code in the company, both found by one question that feature reviews never ask. The fixes were textbook. The finding was not.

Recent entries

Full timeline
  1. Experiment

    The question that found two doors

    Two holes in two days, in a product that sells email security and in the oldest code in the company, both found by one question that feature reviews never ask. The fixes were textbook. The finding was not.

  2. Field note

    Double opt-in was single behind scanners

  3. Field note

    First run of the setup skill, on the whole company

  4. Field note

    The journal learns to write itself

  5. Field note

    The reviewer becomes a pack

Search

Filter results by project and type.