AI implementation

Practical AI, implemented around the way you work.

We help you reduce manual work and connect systems, one workflow at a time. Experienced people assess the process, implement a bounded pilot, connect your tools and train your team, with human review built in.

Implementation is separate from the growth memberships and quoted after discovery. Setup fees may apply.

Example workflowIllustrative
  1. 01 Intake

    A request arrives

    Request type

    New quote

    Details

    Replace unit at second site

    Captured once, routed automatically
  2. 02 Team workspace

    Your team does the work

    • Prepare quoteOwner: estimatorAssigned
    • Check pricingReviewer: managerIn review

    Approval required before it goes out

  3. 03 Client update

    The client sees progress

    Quote approved and sent

    Status, files and confirmation visible to that client only

A simplified example of how a custom application can join up intake, internal work and client communication. Your workflow is mapped in discovery.

What is possible

Workflows and tools we can implement.

Each direction below shows the problem it solves, the features it can include and a simplified illustration. All are separately scoped implementation work.

01 / Client portals

Give your customers one place to look.

Customers email, call and text for updates, and your team retypes the same answers from four different systems.

A secure area where each customer sees only their own requests, documents and account details, and where updates are recorded once.

Possible features

  • Request submission with visible status
  • File exchange for documents and approvals
  • Approval steps with a record of who signed off
  • Account or order information, scoped by permission
Request statusSample

Request

In review

Approved

  • New artwork requestIn review
  • Signed agreement.pdfShared

Illustrative example. Not a live product screen.

02 / Internal tools

Replace the spreadsheet your team has outgrown.

The real process lives in a shared sheet, a chat thread and someone's memory, so nothing is reliably visible.

A tool shaped around how your team actually works, with the steps, fields and permissions your process needs.

Possible features

  • Quote and estimate workflows
  • Project or job tracking with clear ownership
  • Approval and sign-off steps
  • Operational dashboards for the numbers you already track
Job boardSample

To quote

  • Site visit: Elm St
  • Replacement unit

In progress

  • Install: Unit 4

Awaiting approval

  • Change order

Illustrative example with placeholder work items. No real client data or results.

03 / Integrations

Stop retyping the same information.

An enquiry lands in an inbox, gets copied into the CRM, then copied again into a task list, and sometimes gets missed.

One path from enquiry to assigned work, with a record of what synced, what failed and what needs another attempt.

Possible features

  • Website form to CRM record
  • CRM record to an assigned task
  • Notifications to the right person
  • Sync status, error visibility and recovery on failure
Data handoffSample
  1. Website form
  2. CRM record
  3. Assigned task
  4. Notification
  • Sync statePossible: retry on failure
  • VisibilityPossible: error log

What is possible depends on the API access and permissions each of your systems offers. We check that in discovery rather than promising it upfront.

04 / Booking and intake

Ask better questions before the call.

Every enquiry looks the same in the inbox, so qualifying happens in a first call that could have been avoided.

A structured flow that asks only the relevant questions, routes the enquiry and books time when it makes sense.

Possible features

  • Conditional questions that adapt to the answer
  • Qualification and routing rules
  • Scheduling against real availability
  • Confirmations and follow-up reminders
Branching enquirySample
What do you need help with?
New project
  • Budget range
  • Timing
  • Book a call
Existing customer
  • Account lookup
  • Route to support

Illustrative example. Not a live product screen.

How we build

AI accelerates the build. Expertise shapes the result.

AI tooling removes a lot of the repetitive development effort, which helps a budget go further than it would have a few years ago. It does not decide how your data should be structured, who should be able to see what, or whether a system is safe to rely on. People do that, and they review everything that ships.

  1. 01AI-assisted

    Exploration and prototyping

    We use AI tooling to move quickly through the repetitive parts of development: scaffolding screens, drafting data models, trying an approach before committing to it.

  2. 02Expert-led

    Architecture, integration and testing

    People decide how the application is structured, how permissions work, how it connects to your other systems, and what has to be tested before anyone relies on it.

  3. 03Agreed

    Launch and ongoing support

    Launch happens against an agreed scope, and the support arrangement afterwards is written down rather than assumed.

How an engagement runs

Start small. Prove it. Then decide what is next.

  1. 01

    Process assessment

    A workflow map and a written recommendation

    We map how one process runs today, where time is lost, and which step is worth changing first. You get a written scope before any build work starts.

  2. 02

    One-workflow pilot

    A bounded pilot your team can use

    We implement a single workflow, such as inquiry routing or product lookup, with clear limits so it can be judged on real use.

  3. 03

    Integrations and tools

    Tested connections to agreed systems

    Connections to your website, inbox, CRM or product data are built against the access each system actually allows, then tested.

  4. 04

    Human review and training

    Clear approval steps and a trained team

    Your people approve pricing, commitments and anything sent to customers. We train the team on how the workflow works and when to step in.

  5. 05

    Scoped ongoing management

    Optional monitoring and prioritized improvements

    If it makes sense after the pilot, we agree an ongoing scope for monitoring, adjustments and the next improvements. It is written down, not open-ended.

Implementation is quoted after discovery and is not included in a growth membership. There is no published price, setup fees may apply, and nothing is committed before we understand the problem.

Practical questions

Before you get in touch.

What kind of work do you implement?

Practical workflows and tools: product information lookup, inquiry intake and routing, CRM handoffs, draft quote preparation, client portals and internal tools. If the answer is really a better website, we will say so. That is what the growth memberships cover.

Can you work with the tools we already use?

Often, but it depends on what each system exposes. Some tools have a well-documented API and clear permissions; others do not. We assess that first and tell you what is genuinely possible before it goes into a scope.

How does pricing work?

Implementation is quoted after a discovery conversation, separately from any growth membership. There is no published price. An assessment or pilot is quoted on its own terms, setup fees may apply, and ongoing management is scoped separately.

Does AI make decisions for our team?

No. AI can help find information and prepare drafts. Your people stay responsible for product selection, pricing, commitments and anything that goes to a customer.

Do you guarantee time savings or results?

No. We agree what the pilot should do, measure it against real use with you, and decide together whether to continue.

Start with a discovery conversation.

Bring the process that is causing friction. We will map it, tell you honestly whether software is the right answer, and scope it properly if it is.

All insights
  • Connecting your website to HubSpot: a practical decision guide

    What a website actually needs to send to HubSpot, the realistic ways to connect a custom site, what to keep on your own platform versus hosted by HubSpot, and the data hygiene and consent checks that keep a CRM trustworthy after go-live.

    8 min read

  • What HIPAA actually requires of your website forms

    An educational guide for covered entities: when a web form is handling protected health information, what a business associate agreement covers, what the Security Rule requires around encryption, and the questions to put to any form or hosting vendor.

    8 min read

  • Which lead attribution model actually fits your sales cycle

    A practical way to choose between last-touch, first-touch, multi-touch and data-driven attribution based on your sales cycle, channel mix and data maturity — plus why no model proves causation on its own.

    8 min read