Green Guava Tree GREEN GUAVA TREE

Software your team and its AI can keep changing

We help teams take care of the systems they have and set up the ones they are starting, as an experienced hand beside them.

The system you have

Inherited, rushed, or written by AI faster than anyone could review it. We take care of it one part at a time, while the business keeps running.

  • Every release needs a quiet day and someone watching it until the next one.
  • One or two people understand the core of the system, and the business carries the risk of their holidays.
  • The rewrite has been six months away for two years.
  • AI tools made the team faster at writing code and slower at everything that comes after it.
Let's talk

The system you are starting

A new project set up so AI works inside firm rules from the first day, and speeds your team up instead of burying it.

  • A new product is about to start, and most of its code will be written with AI.
  • A prototype built with AI works, and nobody is sure it can grow.
  • The habits your team forms with AI in the next months are the ones it will keep.
  • You want the first year of code to make the years after it easier, not harder.
Let's talk

Built on tools your next hire already knows

The new system runs on widely used, well-supported tools, chosen so it is easy to hire for, simple to run, and never tied to us.

  • Cloudflare
  • Nx
  • TypeScript
  • Effect
  • React

What the years taught us

Every system we have built left a lesson behind, and we bring each one to every team we work with. These are the ones written up in full so far; leave an address at the foot of the page and the next comes to you the day it is out.

  1. Lesson 01

    A new part should ship before the rest is ready

    Each new part is built to stand in for the old one from its first day, so value arrives early and nothing waits on everything else.

    Read the study
  2. Lesson 02

    Keep the history, not only the latest figure

    Every change the business makes is kept as a record, so nothing is lost when a system moves and every number on a report can be explained.

    Read the study
  3. Lesson 03

    Every situation has a planned answer

    Each situation a customer can be in is designed up front, so the software is never caught in one nobody thought of.

    Read the study
  4. All lessons

    Read everything we have written up

    Every case study so far in one place, each with the system it came from, and the next ones as they are written.

    See all lessons

Built this way

Our own products run on the same discipline, in daily use, so everything this page promises has been lived with before it reaches your team.

  • Covalentteam Covalentteam

    A 1:1 rhythm for engineering managers. It installs on a GitHub organisation, says who is due a conversation, and reads their month of pull requests, reviews and issues as one picture before you open it. Nobody is given a number, and a month later it is gone.

    Get to know Covalentteam

  • Pip

    Planning poker, free, with an AI at the table. It reads the story before the cards go down, so the round is spent on the work and not on the number.

    Coming soon

Wherever you are stuck, there is a way in

Sometimes a team just needs an experienced hand. We have spent years inside systems that had to keep running while they changed, and we come as extra hands, a fresh pair of eyes or a mentor, for as long as you need us.

  • The system works, and nobody dares to change it.

    We move it one part at a time while it keeps serving, until the old one can be switched off.

    Let's talk about modernization

  • The project has stalled, and nobody can say quite why.

    A fresh pair of eyes that has seen most of the ways a project gets stuck, and a plan your team can pick up the next day.

    Let's talk about a project rescue

  • AI is writing more code than anyone can review.

    A plain-language account of what is really in the system and where it is fragile, and the rules that keep it from growing back.

    Let's talk about a code audit

  • You have a plan and want to know whether it holds.

    We read it against the system and write back where it will hold and where it will break.

    Let's talk about a second opinion

  • You are starting something new, and want AI to help rather than pile up.

    We lay the project out with the structure and the rules AI tools need to work safely from the first day, so what they write stays something your team owns.

    Let's talk about a greenfield setup

  • The team is stretched, and there is nobody senior to learn from.

    Experienced engineers inside your team, for a few weeks or for the long haul, pairing with your people so the discipline stays when we leave.

    Let's talk about extra hands and mentoring

Keep learning with us

Each lesson above comes to you the day it is written up, with what the work is teaching us now.

  • A letter about the work Now and then, on what we are building and what it has taught us.