Services
Two tiers, and the difference between them is the whole point. First the work with a sample you can open. Then the work that is offered with the system to deliver it and no sample yet.
Work with a sample you can open
Offered, with no sample yet
These are taken on, and the agents and skills that deliver them exist today. What does not exist yet is a sample a stranger can open, so nothing here claims one. Each names the condition that would change that.
In development. Taking enquiries.
- ·. Repetitive work moved into pipelines: document processing, content extraction, reporting, routing.
- ·. Old sites and codebases moved onto a stack that can be maintained, with the content carried across intact.
- ·. The unit of work is one agent with a defined job, the tools it may call, and the boundary it may not cross.
- ·. The connector is the deliverable: a mapping between two record shapes, the retry behaviour when one side is down, and a log a person can read.
- ·. The output is a written verdict: what to build, what to buy, what to leave alone, and the assumption that would change the answer.
- ·. It is not a programme, it is not a platform, and nothing runs on our infrastructure. The work happens inside systems the organisation already owns.
- ·. Scoped to a single outcome rather than to a capability, so there is something specific to measure at the end of it.
- ·. Themes, blocks and the content model, kept simple enough that the people who own the site can edit it without breaking it.
- ·. The builder is both the constraint and the point: the client has to be able to change the page once the work is over.
- ·. Global styles and block patterns first, so the tenth page still looks like the first one without anybody policing it.
- ·. Products, variants, tax and shipping are the work. The theme is the easy part and it is not where stores go wrong.
- ·. Theme work, and apps where the storefront needs behaviour the platform does not ship.
- ·. Pipelines, forms, calendars and the follow up sequence, built as one system rather than as separate switched on features.
- ·. The audit tracks a fixed set of prompts over time and reports share of answers, rather than a position on a page nobody reads.
Work with a sample you can open
Agentic Web Development
Web applications where an agent answers in context, routes a request, or runs a task end to end, with the model layer kept behind a server boundary.
- Sites and apps where an agent does the work: answering in context, routing requests, running a task end to end.
- Built on the Next.js App Router with the model layer kept behind a server boundary.
- This console is the working example. Every command you run here is the same pattern.
Delivered by: architect, code-reviewer, design-director
Skills used: quality-gate, taste
Agent Reliability & Evaluation
Model and agent features put under measurement, so a change to a prompt, a tool or a model is scored against a fixed task set before anyone else meets it.
- Evaluation suites, golden tasks and a recorded baseline, so a quality drop is caught by a run rather than by a customer.
- The same discipline covers ordinary code: automated checks before a merge, and a deploy that either completes or reverts.
- The harness tools on this site are the receipts, and each one is published with the finding it produced rather than a score.
Delivered by: eval-engineer, qa-engineer, code-reviewer, debugger
Skills used: eval-suite, debug-loop, quality-gate
MCP Servers & Assistant Integration
Servers that expose a system's own record to an AI assistant over the Model Context Protocol, with every result carrying the address it was read from.
- A server that publishes what a system already knows, so an assistant can query it directly instead of scraping a rendered page.
- Every tool result carries the address it came from, which is what lets an assistant cite the source rather than paraphrase it.
- This site is its own example, and the tests that pin what each tool returns run in the same suite as everything else.
Delivered by: mcp-engineer, agentic-director, architect
Skills used: mcp-builder, agents-sdk
Agent Ecosystem Design & Audit
An existing set of agents, skills and prompts measured against what it is actually used for, then cut back to the parts that earn their place.
- The audit runs first: which agents get dispatched, which are never called, and which overlap enough that one of them is dead weight.
- What follows is a smaller roster and a written admission standard, so the next addition has to argue for itself.
- The measuring tool is published and openable, and the finding it returned on this ecosystem is on the record with it.
Delivered by: chief-of-staff, prompt-engineer, knowledge-librarian
Skills used: agent-forge, ecosystem-groomer
Full-Stack Development
One engineer owns the database, the API and the interface, so no requirement is lost in a handoff between separate teams.
- Database, API and interface handled by one engineer, so nothing is lost in a handoff.
- React and Next.js on the front, Node.js and PostgreSQL behind it.
- Receipts: the Kredit Hero credit app, 1,000+ users in its first 30 days.
Delivered by: architect, backend-director, devops
Skills used: data-model, ship-it
Project Management & BA
Requirements written down, scoped and sequenced before code is written, by the same person who then builds it.
- Requirements written down, scoped and sequenced before code gets written.
- Agile delivery in sprints with the state of the work visible at all times.
- Receipts: all Kredit Hero sprint milestones delivered 15% ahead of schedule.
Delivered by: product-manager, product-strategist, architect
Skills used: spec-it
Offered, with no sample yet
These are taken on, and the agents and skills that deliver them exist today. What does not exist yet is a sample a stranger can open, so nothing here claims one. Each names the condition that would change that.
AI Automation & Integration
Repetitive work moved into inspectable pipelines that run against the APIs of the tools a business already pays for.
Becomes live when: A pipeline sample a stranger can open is published, with its export and one recorded run. The client work behind this service is real and named on the career record, and none of it is public.
Delivered by: automation-engineer, ai-engineer
Skills used: n8n-delivery, ghl-delivery
Legacy Modernization
Ageing codebases moved onto a maintainable stack by a migration path that is scripted and repeatable, with the content carried across intact.
Becomes live when: One migration a stranger can open is published: the site before, the site after, and the script that carried the content across. The programme behind this service runs on client sites that stay private.
Delivered by: refactor-specialist, architect, data-engineer
Skills used: data-model, spec-it
Custom Agent Building
One agent, or a small team of them, built for a named job inside a business, with a written task it has to pass before it is trusted with the work.
Becomes live when: One client shaped agent is published with its golden task and the evidence from running it, so a stranger can read what it was asked and what it actually did.
Delivered by: prompt-engineer, agentic-director
Skills used: agent-forge, skill-creator
AI Connectors & Integrations
The plumbing between two systems that were never designed to talk, so a record created in one appears in the other without a person retyping it.
Becomes live when: A working connector between two named platforms is published with its export, its field mapping and one recorded run.
Delivered by: automation-engineer, api-designer
Skills used: n8n-delivery, ghl-delivery, api-conventions
AI Consultancy
An outside read on where a model helps a business and where it will cost more than it returns, written down and argued rather than presented.
Becomes live when: One advisory artifact is published in an anonymised form, so a stranger can read the reasoning without reading the client.
Delivered by: cto, product-strategist, ai-engineer, architect
Skills used: deep-research, spec-it
Agentic Transformation for Organisations
One process at a time moved to an agent that runs it, measured against the way that process ran before, with anything that did not improve handed back.
Becomes live when: A local experiment on one real process is finished and its evidence pack is published, including at least one result that came out red and at least one claim that could not be verified. This is the thinnest delivering system on the list: the process analysis specialist the plan wants has not been built, so today it is assembled from general strategy and engineering members.
Delivered by: chief-of-staff, product-strategist, ai-engineer
Skills used: spec-it, eval-suite
AI Solutions
One problem taken end to end: the data it needs, the model call it makes, the interface a person uses, and the measurement that says whether it worked.
Becomes live when: One end to end sample is published together with the measure it was scoped against, and that measure is reported whether or not it flattered the build.
Delivered by: ai-engineer, architect
Skills used: eval-suite, spec-it
WordPress Development
WordPress sites built or repaired by someone who reads the theme and the database, rather than installing another plugin on top of the problem.
Becomes live when: A sample site a stranger can open in a browser sandbox is published alongside its theme source. The procedures that deliver this work exist and are named above; the sample is the only missing part.
Delivered by: architect, refactor-specialist
Skills used: web-qualify, wp-build, web-handoff
Elementor Builds
Pages built in the visual builder a client already uses, kept fast, and kept editable by the person who owns the site after the engagement ends.
Becomes live when: A sample build opens in a browser sandbox with its page structure readable, rather than a screenshot of one.
Delivered by: architect, refactor-specialist
Skills used: web-qualify, wp-build, web-handoff
Kadence Builds
Sites on the Kadence theme and its blocks, set up so the layout stays consistent when someone other than the builder adds the next page.
Becomes live when: A sample build opens in a browser sandbox with its global styles and block patterns readable.
Delivered by: architect, refactor-specialist
Skills used: web-qualify, wp-build, web-handoff
WooCommerce Stores
A store with its products, its tax and shipping rules, and a checkout proven in test mode before a real card is ever presented to it.
Becomes live when: A sample store opens with products, tax and shipping rules configured, and a checkout running in test mode.
Delivered by: architect, refactor-specialist, data-engineer
Skills used: web-qualify, wp-build, web-handoff
Shopify Development
Themes and small apps on a hosted commerce platform, where the platform owns payments and the work is everything arranged around them.
Becomes live when: A development store a stranger can view is published, or a recorded walkthrough alongside a public theme or app repository.
Delivered by: architect, api-designer, devops
Skills used: web-qualify, shopify-build, web-handoff
GoHighLevel Systems
Pipelines, forms and follow up inside the agency platform, wired so a new lead is answered by the system instead of remembered by a person.
Becomes live when: A sample account is recorded and documented, voice configuration included, so a stranger can watch the build rather than read a description of it.
Delivered by: automation-engineer
Skills used: ghl-delivery
AI Search Readiness (SEO / AEO / GEO)
Pages made citable by an answer engine as well as findable by a search engine: entity markup, answer shaped copy, and a record of which prompts return the page.
Becomes live when: This site itself is indexed: verified in a search console, sitemap submitted, and carrying at least one inbound link. A search readiness service whose own site cannot be found is the clearest counter example available.
Delivered by: seo-specialist, aeo-specialist, growth-director
Skills used: ai-seo, programmatic-seo