A.I. PRIME · 001 — Operating Manual

One working AI workflow. Shipped in fourteen days.

For founder-led B2B teams that want operational leverage — not another roadmap, not another pilot.

See how fourteen days looks
AIP-001 / WORKFLOW
live
01
INTAKE
Email · Form · Ticket
02
AGENT
Reasons over your docs
03
ACTION
Reply · Route · Log
04
OUTCOME
Measured, not promised
Day 14 · Shipped
→ Operator hand-off
FITFounder-led B2B, 5 – 50
SCOPEOne workflow, fixed
CADENCEAudit → Launch in 14 days
OUTCOMEMeasured, not promised
Services · 01 – 04

Four ways to start. Pick one.

Easy to understand, easy to buy, anchored to a single practical outcome your team can see inside two weeks.

01

Support Agent

Best for teams answering the same questions daily

An AI-assisted first pass on your inbox — grounded in your docs, escalating cleanly when a human is actually needed.

14 daysfrom $2,500
  • What gets built

    grounded answers from your docs

  • What gets integrated

    escalation rules for edge cases

  • What success looks like

    response-time and deflection tracking

Start here
02

Sales Follow-up

Best for teams losing leads to slow response

Inbound leads qualified and followed up automatically, so the pipeline keeps moving without manual chasing.

14 daysfrom $3,000
  • What gets built

    automated qualify-and-follow sequences for inbound leads

  • What gets integrated

    your forms, CRM or inbox, and clean rep hand-off

  • What success looks like

    time-to-first-touch and qualified-meeting lift you can read weekly

Start here
03

Opportunity Sprint

Best for teams unsure where to start

A five-day sprint that identifies the highest-leverage workflow to automate first, with a numbered launch plan.

5 daysfrom $500
  • What gets built

    ranked workflow audit plus a numbered 5-day launch plan

  • What gets integrated

    your stack map, owners, and real constraints for the first win

  • What success looks like

    one agreed use case with next steps — not another roadmap deck

Start here
04

Knowledge Copilot

Best for teams burning time hunting scattered internal knowledge

A retrieval layer over your SOPs, docs, and wikis so answers show up inside the workflow you are already in — cited, traceable, and without the Slack ping spiral.

14 daysfrom $2,000
  • What gets built

    a cited answers surface over SOPs, docs, and wikis

  • What gets integrated

    the tools you already work in — Slack, desk, browser, or internal app

  • What success looks like

    less ping-pong, faster task completion, traceable sources per answer

Start here
Where we start

The first thing we automate is usually the dullest thing you do.

One repetitive workflow: ship it, then measure it — no roadmap theater.

001Support

Stop answering the same question five times a day.

A support agent pulls from your SOPs and knowledge base, handles the repeats, and routes the rest to the right person with full context.

Reduce repetitive ticket-handling time.

  • Grounded answers — not guessed.
  • Escalation paths you control.
  • Hand-offs include full thread context.
Inbound · support
queue · live
#2041 · password reset#2042 · pricing tier#2043 · refund window#2044 · SSO setup#2041 · password reset#2042 · pricing tier#2043 · refund window#2044 · SSO setup
↓ routed by agent
L1
Auto-answer
Common FAQs
L2
Grounded reply
Retrieved from docs
L3
Human escalate
Edge cases
002Sales

No inbound lead sits untouched for a day.

Inbound is qualified automatically, follow-up runs on a short loop, and warm leads land with the right rep plus notes they can use on call one.

Reduce lead response delay.

  • Qualifies against rules you already trust.
  • First-touch in minutes, not the Monday sweep.
  • Hand-off is context, not just a name and email.
Pipeline · weekly
acme.co · hot
S1
Inbound
acme.co
northwind.io
stellar.ai
S2
Qualified
acme.co
northwind.io
S3
Follow-up
acme.co
S4
Hand-off
→ AE
no lead left sitting
response · under 10 min
003Knowledge Copilot

Answers live inside the task, not across eight tabs.

Retrieval across SOPs, docs, and wikis so people get cited answers inside the tool they’re already in — instead of opening Slack.

Reduce time spent hunting for SOP answers.

  • One place over scattered files.
  • Sources attached so answers are auditable.
  • Less tab-hopping on repeat internal questions.
Retrieval · internal
grounded · traceable
K1
SOPs
K2
Docs
K3
Wiki
AGENT
Reasons
ANSWER
in context
one flow · less context-switching
Process · 14 days

Audit. Build. Launch. Optimize.

The process is narrow on purpose. The first engagement produces a working asset, not a roadmap. Anything wider starts after we’ve shipped something real.

01Day 01

Audit

We map the workflow, tools, and bottlenecks and pick the one place AI will create obvious leverage first.

Delivers Workflow map + ROI estimate

02Day 03 – 10

Build

We design the agent, the prompts, the integrations, and the guardrails around a single, named use case.

Delivers Prompts, logic, and integrations

03Day 11 – 13

Launch

We deploy into your environment, brief the team, and agree on the numbers that tell us it’s working.

Delivers Deployment + training + KPI tracking

04Day 14 +

Optimize

We refine from live usage so the first launch becomes a reliable asset, not a demo that quietly dies.

Delivers Tuning from live usage

Most first engagements stay intentionally narrow: one workflow, one use case, one definition of success.

Who it's for

Built for small teams that would rather ship than deliberate.

B2B SaaS

Teams drowning in repeat support, demo requests, and onboarding questions.

Agencies

Firms that want tighter lead handling and fewer repetitive manual tasks.

Consultancies

Founder-led teams that need leverage without a custom software project.

Service businesses · 5–50

Small B2B operators who want one practical AI win before committing further.

Example outcomes

What a good first win tends to look like.

Mini case simulations — not client names. Picture your version of the same workflow.

EX-01

Support inbox relief

Team

10-person B2B SaaS

Workflow volume

Same fifteen questions eat most of the shared inbox every week — not spikes, just steady drag.

Before

Repeat support questions consuming daily operator time; copy-paste answers and endless triage.

After

Grounded first-pass handling from your docs + cleaner escalation when a human really matters.

EX-02

Sales follow-up consistency

Team

Founder-led consultancy, ~12 people

Workflow volume

Demo requests and trial signups arrive across forms and inbox — volume is modest but timing is brutal.

Before

Response and follow-up depend on whoever is between meetings; good leads cool off by default.

After

Qualify-and-follow runs on a short loop; reps take over warm threads with context, not cold intros.

EX-03

Internal knowledge access

Team

Remote-heavy agency, Notion + Drive + legacy PDFs

Workflow volume

Every new client kickoff starts with ‘where’s the template?’ — same scavenger hunt, different week.

Before

Tribal knowledge and scattered SOPs; answers live in Slack scrollback nobody can search cleanly.

After

Cited answers in the tab you’re already in — fewer shoulder taps, repeatable delivery that stays documented.

Want us to map your version of this workflow?

Founder · 01

Founder-led. Hands-on. No handoff.

A.I. PRIME is small by design — agents, integrations, and guardrails built to survive real inboxes, pipelines, and internal tools, not a conference demo.

FND · 01
Available
Madhawa Adipola, founder of A.I. PRIME

Founder, A.I. PRIME · Hands-on delivery

Madhawa Adipola

One workflow. One owner. One definition of done. Then tuning from real usage.
On the work

Madhawa leads the studio hands-on — agents, integrations, and guardrails, not slideware. The work is built to survive real inboxes, pipelines, and internal tools, not a conference demo.

Why this studio

A.I. PRIME exists because smaller B2B teams are stuck between vague AI roadmaps and tools nobody adopts. You deserve a bounded engagement: one live workflow you can measure before you fund the next thing.

BasedColombo, Sri Lanka
RoleFounder & lead delivery
CraftAgents, integrations, guardrails
About · Approach

We keep the technical sophistication backstage and sell the operational result up front.

Fixed scope is how serious delivery happens at your size — one workflow, one internal owner, one definition of done, then tuning from real usage. Scope expands only when the first win earns it.

Under the hood you still get reasoning, integrations, and human review where they matter — but your team meets a clear, measurable outcome first, not a stack of mystery tickets.

We lead with the outcome — not the jargon. Buy the first workflow, see it work, then decide what else is worth building.

Why fixed-scope
  • Fixed scopeOne workflow. One use case. One definition of success.
  • Fixed timelineFourteen days, start to launch — momentum doesn’t leak.
  • Fixed deliverablesYou know what ships, what’s documented, and what hand-off looks like.
  • Low-risk first stepA real operational result before committing to a broader AI roadmap.
Paired toolsSupporting products that extend the service when relevant — not the main offer.
Next step

Tell us the repetitive thing. We’ll tell you if it’s the right first workflow.

Book the Opportunity Sprint

Let’s find the right workflow to automate first.

Share a little context. One-business-day reply. One-workflow engagement.

Direct

Madhawa Adipola

Based

Colombo, Sri Lanka · Serving globally

Tell us the repetitive task, where it happens, and how often it occurs.