AI consulting

AI that can act.
And knows when not to.

We design AI systems that research, remember, decide, create and operate inside real business workflows, with explicit boundaries around what they can touch and when a person stays in control.

Supervised action · live Awaiting approval
New enquiry

“We are getting traffic but almost nobody books.”

System interpretation

Qualified service enquiry · brand strategy

Proposed action
Send the relevant case study Create the CRM record Schedule a follow-up
Human approval required

The system proposes. A person releases the action.

Record · ENQ-2481 Source · website enquiry Human in the loop
The real problem

AI is easy to demo.
Reliability is harder.

A clever answer is not the same thing as a dependable system.

The difficult questions begin after the demo.

What does the system know?
What does it remember?
What can it touch?
What actions require approval?
How does it verify success?
When does it stop?
System anatomy

A trustworthy agent is designed as a chain of constraints.

01
Context

What it knows

The documents, pages and records the system is allowed to read, and the boundary where that reading stops.

02
Memory

What persists

What is kept between conversations, for how long, and who can see or remove it.

03
Tools

What it can access

Each connected system is a decision: what it may read, what it may write and what stays out of reach entirely.

04
Permission

What it may do

Actions are separated into what runs without asking, what waits for a person, and what is never allowed.

05
Action

What it changes

Every write is named, logged and reversible where the underlying system allows it.

06
Verification

How success is checked

The system has to be able to tell the difference between having answered and having answered correctly.

07
Escalation

When a person takes over

The point where the system stops guessing and hands the decision to someone accountable.

The exception, designed in

Escalation is not a failure state. It is the part of the design that decides what the system is allowed to be wrong about.

Not a screenshot

Use it.

The interesting part of an agent is not the reply. It is the state around the reply: what it used, what it was allowed to do, and where a person had to agree.

User

We are getting traffic but almost nobody books.

System

Before recommending more acquisition, I would inspect the point where interest becomes commitment. Do people understand the offer, see enough proof and know what happens after they click?

User

Then tell me what is broken.

System

I can audit the public pages and show you where confidence breaks. I cannot contact anyone or change your CRM until a person releases that action.

Context used

Website and service model

Tool access

Site audit · read only

Allowed action

Analysis and drafts

Human approval

Required before any outreach

What we build

Start with a workflow. Not with “we need AI.”

Revenue operations
Lead arrives→ Enrich→ Classify→ Draft→ Approval→ CRM
Knowledge systems
Documents→ Retrieve→ Reason→ Cite the source→ Answer
Customer-facing agents
Customer question→ Classify→ Solve→ Escalate with context
Operational automation
Request→ Plan→ Tool action→ Verify→ Report

Blue chips are where the system acts. Orange chips are where a person decides.

Our own systems

We use the same principles inside Pulse.

We sell operating systems we are willing to operate ourselves.

The Pulse AI visibility audit
Audit

Reads the public site and reports what it finds, without being told.

Assistant

Context · public site and service model
Tool access · read only
Memory · none beyond the session
Escalation · a person, on request

The Pulse Growth Engine turning decisions into work
Growth engine

Turns the decisions into ongoing work someone actually owns.

AI visibility

Can machines understand what your company means?

A person reads

“Build for attention. Design for trust. Optimize for choice.”

A human weighs the sentence, the work around it and the reputation behind it.

A machine extracts
OfferWhat is being sold, in one line
EvidenceWhat the business can prove
EntityWhich company, where, since when
AudienceWho it is for, and who it is not
Next actionWhat a reader is expected to do

Being indexed is not enough. AI assistants increasingly interpret a business through its published language, evidence and structure. We examine whether a site is legible to people, search systems and AI without flattening the distinctions that make the business worth choosing.

Tell us what should happen. We will work out whether AI belongs there.

We map the task, the information it requires, the actions involved and where human judgment should remain. If AI is the wrong instrument, we say so.