Answers before you run jobs through Barker.

Barker is sold as a company workspace for tree service operations. Public launch pricing is listed on the pricing page and can change as early-access packaging is finalized.

No. Customers use secure links for estimates, document packets, and payment requests. They do not create reusable customer portal accounts in the first version.

Workers use a scoped field experience tied to assigned work. Billing and packaging are managed at the company workspace level.

The first Barker package is designed to be simple. Any material limits or external-provider costs will be stated before launch.

A company creates a customer, tracks a lead or opportunity, builds an estimate, sends it by secure link, records signature and deposit readiness, then creates a job for scheduling and dispatch.

Yes. Customers can have multiple opportunities, estimates, and jobs at once, each with its own address, notes, hazards, documents, crew, and payment state.

No. Any AI-assisted tree or site information is informational only. Pricing remains manual and controlled by the company.

Yes. Insurance claims, carrier details, supplements, document packets, and customer links are core Barker work areas.

Yes. Barker includes a visual dispatch workspace for scheduling jobs, assigning crews, and moving work through the day.

Workers use phone-number-first SMS login and land in a mobile worker view scoped to assigned jobs.

Workers can see assigned job details and field actions. They do not see pricing, estimates, payment history, broad customer history, or unrelated jobs by default.

Yes. Worker workflows include job status updates, time entries, blocker notes, safety reports, and equipment inspections.

The company sends a secure estimate link. The customer can review the shared estimate and accept it from that link.

Companies can assemble job documents into a packet and send a secure link. The link exposes only the packet content selected for that customer.

Barker supports Stripe payment links and manual payment records, with audit trails for deposits, partial payments, and final balances.

The company that sent the link controls access. Customers should contact that company for a replacement link, updated document packet, refund, or scheduling question.

The company owns its customer, job, document, payment, and operational records. Barker processes that data to provide the service.

Yes. Barker records are company-scoped, and active workflows are designed around tenant boundaries from the start.

Barker reuses secure document-storage patterns where provider uploads can go directly to connected storage while Barker stores metadata and pointers needed for the workflow.

Owner, admin, and sales users use email/password login with security controls. MFA requirements and production security gates are part of launch readiness.

The first usable path is designed around a company workspace, customer records, leads, estimates, dispatch, and worker SMS access. Production launch still depends on Barker-owned infrastructure and external service setup.

Import support should be reviewed with Barker support before use. Imports are best-effort and may require manual cleanup, mapping, and validation.

Expected services include hosting, database, storage, email/domain, Stripe, Allo SMS, DocuSeal, and any approved AI provider used for tree or site assistance.

Not until production infrastructure, key rotation, provider setup, live smoke tests, and final launch audit are complete.