Coral Tree.
Approach

Your AI problem is specific. So is how we approach it.

Coral Tree doesn’t apply generic frameworks to specific problems. Every engagement is scoped to what’s actually needed — by people who’ve built and run production AI systems, not by analysts working from a playbook.

01The first conversation

Every engagement starts the same way.

Before any scope is written, five things have to be clear. The diagnostic answers them — then converges on a single written scope.

01

The actual question

What you're trying to resolve. Not the symptom; the decision underneath it.

02

What you know

What's solid, what's assumed, and where the real uncertainty sits.

03

Your constraints

Team, compliance, cost, timeline. These shape the direction before any work begins.

04

What's been tried

Most clients have formed a view or attempted something. What was it, and what happened.

05

What done looks like

A specific outcome, at a specific threshold. Not "better AI." Defined.

The output →

One written scope. Not a proposal.

The entry point
The architecture direction
What we will — and won't — do
What happens if it changes

If part of it isn’t worth building, you hear that here — before anything is agreed.

02Engagement types

Four shapes. The problem decides which.

They aren't products — they're working relationships. Scan across; the right one is usually obvious.

Sprint.

Clarity before commitment.

Timeframe
2–4 weeks
How we engage

A focused two-to-four-week burst.

The output

A written architecture recommendation and build plan.

Right when

You're at a decision point and want an outside read first.

Fractional.

Senior judgment, on call.

Timeframe
Ongoing
How we engage

Biweekly calls, async in between.

The output

Architecture reviews and decisions, as they arise.

Right when

Strong team, no senior AI hire — yet.

End-to-end.

We own the outcome.

Timeframe
Project · months
How we engage

Embedded and weekly, through production.

The output

A system in production, documented, yours.

Right when

Zero to production on a serious build.

Due Diligence.

An independent technical read.

Timeframe
1–3 weeks
How we engage

A fast, intensive audit.

The output

A structured report — findings, not impressions.

Right when

Capital, an acquisition, or a board call is on the line.

03How scope works

Written before the work starts.

01

We scope before we propose

The scope follows the diagnostic — never a template applied to a problem we don't understand yet.

02

We tell you what not to build

If part of the plan isn't worth building, you hear it before any work is agreed. That's the job.

03

Changes go in writing first

Scope shifts get surfaced and agreed in writing — then the hours happen. Never the reverse.

04 · Start somewhere

Every engagement starts
with an hour.

Bring the problem as you understand it. We’ll sharpen it, tell you which shape fits, and show you what working together would look like.

Brief us on what you’re working on →or reach us at hello@coraltree.ai