Skip to content

Business intelligence · AI systems · implementation

AI systems built for your company’s work.

Systems that investigate questions, use company knowledge and prepare or carry out agreed actions. Built with your information, tested on your tasks and introduced with your team.

Tell us about your business What happens during the review
A personal conversation in a bright local office
Your company already holds useful knowledge.

The review shows where AI can use it to answer questions and take on work.

The first release handles a defined job

We agree the inputs, expected outputs and exceptions. Your team tests it with representative cases before it becomes part of daily work. We include instructions, access handover and the ongoing costs in the proposal.

We quote the review before starting. Implementation and ongoing support are separate decisions.

A question from the business

Read a proposal, open the supporting records and inspect the next steps. These examples use fictional data.

Can we take on this project, and what should our proposal say?

Prepare a proposal, but clarify two requirements first.

The request matches the work described in your project library. The requested four-week delivery is shorter than the six weeks in your current plan, and weekend support is not covered by your standard terms.

Customer project brief Previous project library Capacity & service terms
See what this is based on
Source records
Customer requestCompany informationAction needed
Comparable workTwo relevant project referencesUse approved examples
Delivery in 4 weeksCurrent plan allows 6 weeksAgree capacity or a later start
Weekend supportNot in standard termsClarify coverage and price

This example does not establish technical feasibility or a binding delivery date. A responsible person reviews both before making a commitment.

See the proposed next steps

Prepared for review

  1. 1Assemble a draft proposal from the relevant project references and approved service information.
  2. 2Prepare delivery options and questions about weekend support, with sources for each assumption.
  3. 3After the owner reviews scope, price and commitments, prepare the agreed response and internal project brief.
Example of the prepared draft

Thank you for the brief. We have two relevant project references to discuss. Our current delivery plan allows six weeks. Before proposing a four-week schedule, we need to confirm additional capacity and agree what weekend support should include. Could you confirm the required coverage hours?

What we can build

The choice depends on your process and existing software. For each project, we first establish what the tools support and what is useful in daily work.

Investigate business questions

Read offers, conversations, time records and costs together. Answers show the relevant evidence and separate observations from open questions.

Use company knowledge in decisions

Bring internal rules, previous work and approved documents into new tasks. The system prepares options and drafts for your team to review.

Carry work across your tools

After the agreed approval, create tasks, update information and follow up on results. We connect the necessary systems with the right permissions.

Improve against real cases

Test representative tasks, difficult exceptions and feedback from daily use. Improve the system against documented results.

What the handover includes

Tests with your team, the agreed account access, a description of the workflow and instructions for handling failures. We document the running software costs and responsibilities for changes and maintenance. Ongoing support can be agreed separately.

Not sure where to start? See the business review

Our implementation guarantee

If it fails the agreed test, the fix is on us.

Before implementation, we put the acceptance criteria in writing. If our work doesn’t meet them, we correct it at our expense. The final payment for that stage is due after acceptance.

For example: an enquiry from an agreed channel must reach the right queue, contain the required details and flag anything that needs a person. We check it together against the cases agreed before work starts.

What we agree before starting

We agree in writing what to build, how and when to test it, and what each side needs to provide. Extra work gets a separate quote.

And when the problem starts before the enquiry?

We also check whether customers can find you in Google, ChatGPT and other AI answers. Website and business-profile work can be commissioned separately or included in the wider review.

See our search and AI visibility services

From our website audit

574 property pages were missing from the sitemap.

What we found when auditing a real-estate website. The findings and their implications are documented in the case study.

Read the audit

Before we speak

Do we need to know what AI should do?

No. Tell us which decisions or tasks take too long. The review identifies useful applications and checks whether the information needed is available.

Does the review include implementation?

The review gives you the findings and a plan. You decide which changes to commission, at a price agreed separately.

Do we have to replace our software?

We start with your current tools. If we recommend replacing one, we explain why, what it costs and how to make the switch.

How much time do you need from our team?

We agree who needs to be involved and schedule time with them before starting. The 1–2 weeks cover the tasks agreed with you.

Which question takes too long to answer?

Tell us about a decision, investigation or task that needs information from several people or systems.

We quote the review before starting. Implementation and ongoing support are separate decisions.

Where should we start?

Choose one, or describe the task below in your own words.
  1. 1Your task
  2. 2Contact details