Short accounts of real engagements: what we found, what we built, what changed. Client names are withheld where the client prefers; the systems and the numbers are as they were.
A large implementation was being run, faithfully, out of thirteen spreadsheet tabs. Requirements, fit/gap analysis, test scenarios and results, status, and the defect log — all of it, updated live by the team every day. Knowing where the project stood meant reading all thirteen.
The spreadsheets were the system of record and they worked — people knew them and kept them current. The cost was everything downstream: someone had to read them all, write the status, and remind each tester and defect owner what was due. Every day.
An end-of-day run. The latest tabs go to an AI-driven process that produces:
Every one of them carried the client’s and the project’s branding, so it read as project material at a glance.
Nobody had to change how they worked — the spreadsheets stayed exactly where they were. The daily reading, writing, and chasing stopped being a person’s job. Status went out every evening without anyone composing it, and testers heard about past-due work from the system, not from a project manager.
Once the system was live, three questions mattered to leadership: is it stable, are tickets being worked quickly, and how do the people using it feel? The evidence lived in three unconnected places.
The vendor emailed usage and system reports daily. Incidents were tracked in a separate log. Stakeholder sentiment was collected by polling. Each was informative alone; none answered the stability question on its own.
A daily and weekly stability dashboard that combines all three: the vendor’s emailed reports, the incident log, and the polling results with stakeholder feedback. Interactive, branded to the client and the program, and sent to stakeholders every day.
One view of how the system was being used, how quickly tickets were closing, and how project leads were perceived — refreshed daily, in everyone’s inbox, for the whole hypercare period.
The client’s Microsoft Teams plan didn’t include automatic meeting summaries. Summaries were needed almost every day, and they had to read like a professional wrote them — consistent, polished, and actionable.
Transcripts existed; turning them into something a stakeholder would read was manual work, and the result varied by who did it that day. Procuring a new add-on would take longer than the need could wait.
A custom tool that lives in a single portable HTML file. Paste the raw transcript, choose the AI you want to use, pick the formatting and what to include, and generate. Then edit in-line, drag sections into the order you want, and send.
Daily summaries that look the same every day, produced in minutes, with nothing new to procure or administer.
Over a long implementation, decisions get made in meetings and then get made again, because nobody can find the first one. Action items drift. The second brain was built so that neither happens.
Meeting notes were being taken, but they were notes: no consistent record of what was decided, by whom, or who owed what by when.
Every meeting’s notes are turned into a polished summary that carries the key decisions and the action items with assignees. Consistently formatted and branded to the project, all of it lands in a project knowledge base that can be asked questions: what did we decide about X, what’s still open, who owns it.
Past decisions get revisited from the record rather than from memory. Action items get followed up because the system knows they exist. It is the same pattern we set up for clients of every size — and this is where it was proven.
Not every client is a company. This one was a fantasy pick’em league — a group of individuals who wanted recaps, standings, and advice without anyone doing the work. Picks live on the league’s fantasy site; the system imports them at game lock, ingests results, and publishes weekly recaps and personal coaching for every member, automatically.
Picks and results pull in after the fantasy site reveals them at game lock. Each week publishes a newspaper-style league recap, private performance trends and a strategy report card for each picker, and league math that explains why an outcome mattered — who took the lead, which confidence miss hurt most.
Consumer software gets the same standard as enterprise software. Logged, reviewable, reversible — the rules we hold every agent to — are easiest to see in a system with no excuse for cutting corners. This one has none.
Tell us what’s not working. We’ll tell you what we’d look at first.