ashiba.ai
Features ▾
PricingLive demoCase studyAboutSign inStart free
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
The API and MCP server are live.
The REST API v1 and the MCP server ship today — read and write across your projects, cost lines, checklist, schedule, logs, bids, payments, permits, and documents, with role-scoped keys. Call the endpoints directly (REST API reference) or point Claude or any MCP client at the tools (MCP reference). Webhooks are what's next — and we won't publish a reference for endpoints that would 404.
PLANNED
Team-management writes
Invite teammates and change roles over the API — the last domain object still UI-only. Every other object already reads and writes over REST and MCP: projects, cost lines, bids, payments, draws, change orders, checklist, schedule, logs, documents, permits, inspections, punch, leads, vendors.
PLANNED
Webhooks
Push events (a signed change order, a passed inspection) to your own systems.
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.
Start free
ashiba.ai
THE BUILDER'S FIELD OFFICE
足場 ashiba — the scaffolding you stand on to build.
PRODUCT
COMPARE
RESOURCES
COMPANY
LEGAL
© 2026 ASHIBA.AI · AUSTIN, TEXAS