Inquiry pipeline
Capture leads from your site, triage by status, and keep every conversation tied to the right branch.
SaaS · multi-branch ready
One platform for the business on the road and the office behind it. Each company works in its own branch context—so data stays separated today and scales when you open the next site tomorrow.
Running a service company? See the B2B overview →
Built for many businesses, not one spreadsheet
Whether you run a single van or a network of branches, the same product adapts: customers submit requests here; your team signs in and only sees what belongs to their branch.
Three core modules work together so front desk, dispatch, and warehouse stay aligned—no matter how many teams you onboard onto the product.
Capture leads from your site, triage by status, and keep every conversation tied to the right branch.
Plan installs and service visits with clear statuses—from booked to completed—without spreadsheet chaos.
Track quantity, units, and movement logs so each location knows what is on hand before the van rolls out.
Illustrative tiers for a multi-tenant SaaS rollout—adjust numbers and contracts when you go to market. Architecture is already branch-aware.
Free
during MVP / beta
One branch, full core modules—ideal to pilot with your crew.
Custom
per month, per branch
For shops adding locations, dispatch rules, and tighter ops.
Enterprise
annual agreements
Franchise groups and regional chains that need governance.
Taxes, currency, and contract terms are not final—this block is for positioning and demos.
Straight answers for operators evaluating the product—or your own tenants reading the marketing site.
Every record is tied to a branch_id. Staff sign in with a JWT that carries their branch, so lists and updates never leak across branches. When you add more locations, you add branches—not a new database.
Yes. The product is designed so each tenant’s operations are scoped by branch. Other customers never see your inquiries, jobs, or stock as long as auth and API rules stay enforced (the default in this codebase).
For white-label demos, set NEXT_PUBLIC_WHITELABEL_LOGO_URL to a hosted image and optionally NEXT_PUBLIC_WHITELABEL_NAME. The nav shows your logo slot + name; replace assets per tenant when you host separate builds or add runtime theming later.
The public form posts to your API and stores rows under the default branch (branch 1) unless you extend routing. Staff on that branch see them in the Inquiries screen and can move status from pending to done.
That’s a business decision—this UI shows example tiers (Starter / Growth / Scale). The app structure supports per-branch billing when you connect a payment provider and entitlements.
Customers use this form to reach your team. Submissions are stored under the default service branch so routing stays consistent until you add more locations.
Are you a partner business?
Use staff sign-in or read the for-business page for how teams adopt the product.
Public form
Send us your details