ashiba.ai
FeaturesPricingLive demoAboutSign inRequest access
SUPPORT
Knowledge basePlatformContactOpen the app
How can we help?
Browse the topics below, or write to a person who has poured a slab.
POPULAR: setting up bands · inviting a sub · client portal branding
Start here
Setting up your first project
From spreadsheet to field office in an evening.
Estimating
Bands, actuals & verdicts
The flywheel, explained with real numbers.
People
Subs, clients & permissions
Links, grants, and what each role sees.
Field
Checklist, log & documents
The daily tools, phone-first.
Trackers
Procurement, bids & inspections
Order-by dates, COIs, and the gates.
Account
Export & security
Your data and your keys.
Field notes — most read this week
How wide should a band be?
Confidence intervals for lumber, not statistics class.
3 MIN
Inviting a sub who hates apps
One link, no account — what they actually see.
2 MIN
Branding the client portal
Logo, company name, and the first share.
2 MIN
What “projected at completion” counts
Actuals + commitments + band midpoints, exactly.
4 MIN
Recording an actual from an invoice
The 20-second evening ritual.
2 MIN
Still stuck?
Write to a person who has poured a slab.
Answers within one business day — usually the same evening.
Open a ticket
System statusALL CLEAR
Hosted on Vercel · status
SUPPORTKB-014
SUPPORT / ESTIMATING
How wide should a band be?
UPDATED JUL 2026 · 3 MIN READ
A band is a confidence interval, not a wish. The low is “if everything quotes clean,” the high is “if I have to take the second-best sub.” If you'd be genuinely surprised outside the band, it's right.Rules of thumb from real jobs: commodity materials with a signed takeoff — ±15%. Trades you've bid before — ±25%. Anything with a lead time over two weeks — widen the high and flag it, because rushed replacements are never cheaper.
A band that never breaks is too wide to teach you anything. One OVER a job means your estimating is honest.
Was this useful? Yes · NoNEXT: RECORDING ACTUALS →
PLATFORMAPI & MCP · IN DEVELOPMENT
A public API and MCP server are on the roadmap.
They aren't live yet, so there's nothing to point a key at today — and we won't publish a reference for endpoints that would 404. Here's what we're building, and the rule it will hold to.
PLANNED
REST API v1
Read and write every object you can reach in the app — projects, cost lines, checklist, log, documents — with role-scoped keys.
PLANNED
MCP server
Drive the same object model from Claude or any MCP client, scoped to your role exactly as the app is.
PLANNED
Role scoping
Cost and margin fields will be stripped from any sub- or client-scoped key, enforced server-side by the same access rules as the pages.
The same rule the app already enforces will hold at the token: a client- or sub-scoped key will never carry a cost or margin figure. Want early access when it ships? Tell us what you'd build.
Request access
ashiba.ai
THE BUILDER'S FIELD OFFICE
足場 ashiba — the scaffolding you stand on to build.
PRODUCT
RESOURCES
COMPANY
LEGAL
© 2026 ASHIBA.AI · AUSTIN, TEXAS