The guardians
Three checkers that read what was written and say exactly which rule it broke.
a brand guardian and a house-style scanner run across both company systems, and a price proofer checks an 823-row catalogue
THE PORTFOLIO
Capabilities
What the system does, beyond the documents it produces. Each one runs in production; each sample was regenerated for a fictional company.
30 projectsExplore. Inspect. Try it.
Adapt, don’t design
The rule that keeps AI output on brand: start from an approved template, fill the slots, escalate the rest.
the anatomy plus swap-mark pattern is the standard skill shape in both company systems
Find anything in seconds
One reorganization and a generated index, so people and agents both stop guessing which file is current.
logo kits and URL reference indexes in both company systems, so the assistant cites the published link instead of inventing a path
Decks that come out on brand
Thirty layouts, light and dark, native charts, and a render check that looks at every slide.
30 layouts in light and dark against a 60-slide master, with 12 decks approved in one company system
The executive summary
Two pages an operator can read in four minutes, with the decisions pulled to the front.
7 executive summaries generated from the same skill in one company system
One source, a web page and a PDF
The HTML twin and the render check that refuses to publish a document that does not fit its page.
1,157 HTML twins in one company system, all generated rather than maintained by hand
A messy export becomes a workbook
Ingest the export nobody wants to clean, and hand back a workbook with the rejects listed.
workbook ingestion in both company systems, including one workbook of 44 program tabs distilled into a fact table
Web pages, assembled not designed
A shippable page in minutes, from approved sections, with the accessibility numbers measured.
partner microsites and landing pages built from one section library, with the same checks that gate the documents
A human decision outranks the data
When a person overrules a source, the system remembers who, why, and until when.
a decision record file governs the fields where a person has overruled the data in one company system
Pictures of prices became verifiable text
Parse, join to the authority, render, then verify every figure independently.
a rebuild of 1,107 rows produced 223 corrections, and every one verified clean
The sales desk
Three agents that each produce one document, and each stop when a fact is missing.
Staged in both company systems with their gates defined. These are run by a person, not left running on their own
One brief, a whole campaign kit
Flyer, terms, email, social, landing section, and checklist, all generated from the same brief.
campaign kits for promotions, first-order offers, and rebates in both company systems
The launch operating system
A tracker with gates, a day-one playbook, a media plan, and the retention engine that runs afterwards.
a 191-item launch tracker with a day-one playbook, a media plan, and a retention engine, built for a launch that stays confidential until it ships
Audience, tone, and channel
Pick who you are writing to, in what tone, on what channel, and see the rules that decide the words.
an audience, tone, and channel rule matrix in both company systems
The publish gate
The site republishes itself every half hour, and a broken link stops the publish.
a self-publishing pipeline that runs on a half-hour cycle, diffs the manifest, regenerates what changed, and aborts on a link audit failure
What has gone stale
A board that says what is overdue, who owns it, and which generated file no longer matches its source.
freshness telemetry, batch boards, and a twin drift checker across both company systems
Dashboards an operator opens
Revenue, executive and pipeline views computed in the browser from one data file.
revenue and executive dashboards, plus a predictive sales dashboard built at a prior role
One place everyone works
A shared spine, a five-stage work zone per person, and an approval route with a record.
a canonical shared store with per-person work zones and an approval step, in both company systems
Packaged so it survives you
Skills, agents and guides bundled so a team can install them without a walkthrough call.
plugin guides and organisation-wide skill install packages in one company system
The record decides what you may say
A customer record is context, not decoration, and it can veto a message.
a CRM used as context for generated messages, plus a partner dashboard stopped at its feasibility gate before any code was written
Images at volume, honestly
Scripts that generate and index thousands of assets, and a rule against inventing one.
141 image and graphic generation scripts, and a library reduced from 5,959 paths to 1,172 unique assets with a CSV index
The spine that holds it together
A constitution, a routing table, a question register, a decisions log, and a changelog that records its own corrections.
a constitution, routing table, question register, decisions log with supersession tracking, and changelogs of 126 and roughly 100 entries across the two company systems
It reads a card, not the file
Two hundred and forty small cards stand in front of the documents, so a request costs a few hundred words.
a card layer of 241 cards, including 144 partner guides, so the assistant reads a card instead of a 200 kilobyte file
The finding nobody wanted
Twenty-one verifiers read every draft with fresh context. One caught a promise that existed nowhere.
21 fresh-context verifiers over 7 drafts, which caught an invented service-level promise that had already passed a human review
What we do not know
Competitor dossiers with a confidence on every claim, and a gaps file the system will not guess around.
competitive dossiers, domain research, and known-gaps and roadmap files in both company systems
The front door
A vague request gets scored, then asked two or three questions that actually change the answer.
a prompt enhancer front door that scores an incoming request and asks two or three multiple-choice questions from a register
Who may see it, who may run it
A confidentiality ladder, roles that resolve to an answer, and the commands only an operator may run.
a confidentiality ladder with rules for personal and regulated information, role-based access, staged agents, and operator-only commands
The first real task
Ten minutes to read, fifteen to set up, and a concierge that hands you your first job.
a ten-minute onboarding document, a fifteen-minute teammate setup, an onboarding concierge prompt, and a team handbook
The assistant that will not guess
A small chatbot whose whole value is what it refuses to answer.
a starter chatbot a team runs with their own key, which refuses to invent prices or turnaround times
Find the sentence it came from
A meeting becomes decisions, actions and questions, each traceable back to the exact turns.
a scribe that distils meetings into a fixed schema with decisions extracted, in both company systems
No projects match that combination.
Try another term or clear the filters to see all work in this category.