Maslow AI
LET’S TALKLET’S TALK

HOW WE ENGAGE / BUILD WITH A PURPOSE

One useful step. Then the next.

A setup project can be small. A knowledge system needs more discovery. We agree on a scope, a fee, and what would make the work worthwhile before implementation begins.

Talk through a workflowExplore starting scopes

FROM A QUESTION TO A WORKING SYSTEM

See how the work takes shape.

An engagement uses the parts of this process its scope needs. Every phase ends with something your team can inspect.

Skip the guided view
01Understand

Meet the work where it happens.

We start with the people doing the task, the sources they use, and the decisions that matter. Existing systems shape the scope.

Observe
The current task
Map
Sources and owners
Choose
A useful test

ResultA scope and a decision to proceed, refine, or stop.

02Prove

Test the difficult part early.

A focused proof uses representative information and questions. We agree what good looks like before judging the result.

Sample
Relevant information
Test
An agreed baseline
Review
Results and gaps

ResultEvidence to decide whether further implementation makes sense.

03Connect

Put the pieces around one workflow.

We configure the selected knowledge, tools, permissions, and review steps. Your team sees the work take shape and tests the result.

Knowledge
Scoped sources
Workflow
Tools and approvals
Acceptance
Tested with your team

ResultAn implemented scope with documented limits and acceptance evidence.

04Make it yours

Leave your team able to use it.

We work through operation, changes, and recovery with the people taking it on. Training and ongoing support are scoped to what your team needs.

Enable
Practical training
Document
Runbooks and ownership
Operate
Your team or scoped support

ResultA handover, clear responsibility, and a maintenance decision.

Explore scope and handover

YOUR PART

Bring the people who know the work.

A workflow owner, a technical counterpart, and access to representative information make the first test useful. We agree the time commitment and access needed for your scope.

OUR PART

Keep the work visible.

You work with a founder-led team. Progress, decisions, evaluation results, and deliverables are documented so your team can understand what has been built and what comes next.

A larger option: the 90-Day Foundation

For organizations ready to connect a knowledge system and a first supervised workflow, we offer a scoped 90-Day Foundation. Its decision gates sit at weeks 2, 4, and 10. It is one engagement option; smaller scopes do not inherit this timeline.

  1. DISCOVER

    WEEKS 1-2 · LEARN THE WORK

    We shadow the people who do the job today, map the workflows, inventory knowledge sources, and document key-person risks. Technology choices come after this work.

    PLANNED DELIVERABLEWORKFLOW MAP + OPPORTUNITY RANKING
    GO/NO-GO · END OF WEEK 2
    Choose whether to fund a proof around the highest-ranked workflow, refine the scope, or stop with the map.
    WHAT YOU RETAIN
    The workflow map, source inventory, and opportunity ranking produced to date.
  2. VALIDATE

    WEEKS 3-4 · PROVE THE VALUE

    We build a working proof with your data and questions, then measure retrieval quality against an agreed baseline. If the result does not clear the bar at the week 4 go/no-go gate, we stop and you keep the map.

    PLANNED DELIVERABLEPROOF OF VALUE + GO/NO-GO
    GO/NO-GO · END OF WEEK 4
    Continue only if the working proof clears the agreed retrieval-quality baseline.
    WHAT YOU RETAIN
    The working proof, evaluation questions, baseline definition, and results produced to date.
  3. BUILD

    WEEKS 5-10 · BUILD THE FOUNDATION

    We build the knowledge system first, followed by controlled workflow execution and then the AI employee. The first deployment runs in one channel with human approval for consequential actions.

    PLANNED DELIVERABLEPRODUCTION FOUNDATION + FIRST AI EMPLOYEE
    GO/NO-GO · END OF WEEK 10
    Approve the first supervised production workflow only when ownership, controls, and human approval boundaries are agreed.
    WHAT YOU RETAIN
    Knowledge-system and workflow-control artifacts, deployment configuration, and documentation produced to date.
  4. HAND OVER

    WEEKS 11-12 · HAND OVER THE KEYS

    Your team learns to direct, correct, and audit the system. We deliver playbooks and dashboards, then your IT team takes over or uses managed operations until it is ready.

    PLANNED DELIVERABLETRAINING + PLAYBOOKS + OPS DECISION
    OPERATING DECISION
    Choose client-operated ownership or managed operations after the training and handover review.
    WHAT YOU RETAIN
    Training playbooks, dashboards, code, pipelines, skills, and operating documentation in your repositories.

4 phases, with a go/no-go decision before expanding the work. Scope, fees, ownership, and exit terms are set out in your proposal.

Fixed fees are quoted before work begins. Ongoing operations is scoped separately. Hardware, model usage, and third-party services are identified as separate costs.

LET’S MAKE IT USEFUL

Let’s agree on a sensible first scope.

Bring the work you want to improve. We will explore the people, information, and systems it depends on, then agree on a sensible starting scope.

Talk through a workflowMap a workflow first