How Engagements Work

One question. One working view.

Tolowa has broad capability. Your first scope should not. We begin with the part of the business you most need to see, trust, or control.

Show Us What You Can’t SeeSee Pricing

Three entry paths

The budget owner should recognize the problem.

Market System

The company is difficult to understand, trust, or refer.

Can include

Category and offer, proof, information architecture, premium website, CMS, analytics, and conversion paths.

Not this

A cosmetic redesign disconnected from the commercial system around it.

Revenue System

Opportunity exists, but pipeline, follow-up, referrals, or campaigns are improvised.

Can include

ICP and offer refinement, CRM, attribution, signal wiring, nurture, campaigns, content, and pipeline cadence.

Not this

A promise to manufacture demand for a company without a credible offer or accountable seller.

Operating System

Execution depends on founder memory, scattered context, or unreliable handoffs.

Can include

Operating hub, ownership, workflows, dashboards, decision records, meeting rhythm, alerts, memory, and AI routines.

Not this

Installing a workspace and hoping behavior changes by itself.

The System Sprint

Ten business days. Something real goes live.

The Sprint is the normal first paid engagement. It proves how Tolowa works without asking the buyer to approve a company-wide transformation first.

Typical investment · about $5K

01

One named business constraint and baseline

02

One defined system boundary

03

One live workflow, surface, or operating loop

04

One accountable client owner

05

Acceptance criteria and evidence

06

Documentation, handoff, and expansion recommendation

Qualification

A good fit has an owner, urgency, and a question worth answering.

  • A decision-maker is directly involved
  • The constraint matters within the next 90 days
  • The company has customers, evidence, or a credible path to them
  • Someone can own the system after handoff
  • There is willingness to measure the starting condition

Reasons to say no

Capability does not make every project responsible.

  • A cheap standalone website is the entire ask
  • The company expects tools to solve product-market fit
  • No client owner can make decisions or maintain the result
  • The scope depends on unlimited access to the founder
  • The requested outcome cannot be observed or verified

Need to think out loud?

Talk the situation into a working scope.

The Scope Builder captures the business context, desired outcome, existing systems, and constraints before the first conversation.

Open the Scope Builder →

The first decision is
what not to build.

The Visibility Session names the question and the smallest credible next step.

Show Us What You Can’t See