Choose Your Plan

Entry point. We map your manual operations, surface the top automation candidates, and run a back-of-envelope ROI on each.

• Operational scan across sales, support and ops
• Top automation candidates ranked by impact
• Indicative ROI per workflow
• Recommended next step — Discovery Sprint or straight to build

Your site answers AI agents with facts you confirmed: what you do, prices, hours, addresses, questions and answers. An agent that comes to you gets them right.

• An MCP server and an A2A card for your site
• A check that search and assistant robots can open your pages
• Requests from agents, and visitors from AI assistants counted
• WordPress plugin, Next.js package, or REST and a webhook
• Nothing is published until you confirm it

For a business customers find nearby: the Google profile, the city on the site and the markup put right, with the Google Maps check run before and after.

• Google Business Profile verified and tied to the site
• Your city and area named on the homepage
• LocalBusiness markup with address and phone
• The Maps check before and after

Crawler policy, the Schema.org graph and the identity files put right, then the same audit run again so the change is measured rather than claimed.

• Crawler policy written for the assistants that answer
• Schema graph and identity files made consistent
• The pages an engine cannot retrieve, with the reason for each
• Opening and closing audits on the same checks

A site repaired once drifts back. The measurement keeps running on the same frozen prompt set, what it finds gets implemented, and both readings sit side by side every month.

• Weekly re-audit, same checks, same prompts
• Up to 10 fixes implemented a month
• Referring-domain classification and the disavow kept current
• Competitor cohort re-measured
• One working session a month

For a system that already exists, whoever built it. We stand it up from the repository, read what it depends on, and say whether we can be responsible for it.

• Repository, hosting, environment and secrets read
• Database, backups and integrations checked
• Monitoring put in and the deployment documented
• Recovery procedure and the critical risks named
• One of three answers: as is, after stabilization, or replace

The takeover prescribes it when the system cannot be taken over as it is. It covers only what has to hold before somebody is on call, and adds no new features.

• Deployment that reproduces, in Docker where it was not
• Migrations, backups that restore, secrets out of the code
• Error handling, logs and monitoring
• Basic tests and the obvious security holes closed
• Ends with the system entering Care

Process maps, data sources, integration plan, validated ROI model, and the implementation backlog you can act on with or without us.

• Process maps for selected workflows
• Data and integration inventory
• Validated ROI model with assumptions
• Prioritised implementation backlog

A website that books the job, takes the payment and shows the client where things stand, built on the same platform as our own products.

• Up to eight service pages
• Online booking with reminders
• Deposits or invoices paid online
• A client account with booking, order and job status
• The INITE assistant and markup that AI agents can read

We keep a system running, whoever built it: ours, yours, a freelancer's. One envelope per system, agreed in the statement of work, in three sizes.

• Monitoring, alerting and backup verification
• Incident response inside the agreed window
• Dependency, model and API compatibility updates
• Security patches
• A small monthly change budget; new features quoted separately
• Monthly health report