Roles

Built for the people who actually keep the shop moving

Different jobs need different visibility, different actions, and different kinds of confidence. Home Base is built around that instead of forcing the whole shop through one generic view.

Owner visibilityWriter flowManager intervention

Start the 14-day trial Back to platform

Owner

needs the business read

Leadership-level visibility without pretending owners want a pile of raw screens.

Writer

needs flow and follow-through

Service writers feel the pressure when context, approvals, and updates fall apart.

Manager

needs earlier signals

Managers need earlier signals while the day is still salvageable.

Tech

needs low-friction context

Technicians need a clean way to add progress and proof without getting buried in admin.

Role spotlights

Why Home Base matters at each seat

Role-specific relevance matters because each seat feels the shop break in a different place.

For owners

Understand pipeline, production, customer approvals, and closeout momentum from one system of record.

For service writers

Keep estimates, updates, messages, and work-order changes in one operating flow instead of rebuilding context repeatedly.

For managers

See stalled work, overloaded queues, approval lag, and shop risk before they become tomorrow's explanation.

For technicians

Capture progress, support trust, and contribute proof from the bay with less friction and less ambiguity.

For parts teams

Work from cleaner demand, reservation, and issue signals so inventory decisions are less reactive.

For sales teams

Carry lead and quote context forward so the service experience starts from a stronger, better-informed handoff.

Decision lens

Good role pages show what each person needs to know sooner.

That is the real value of role-aware software: not personalization for its own sake, but faster judgment with less confusion.

Questions owners ask

Owners need these answers fast.

1Where is work stalling right now?
2How quickly are approvals moving?
3What is actually ready to close out and bill?

Questions service writers ask

These tend to define the front-desk experience.

1What changed on this job?
2What does the customer still need to approve?
3What context do I need before I call or message them?

Questions managers ask

These are the questions reporting and alerts need to reinforce.

1What requires intervention now?
2Which queues are getting heavier?
3Where are we leaking time, clarity, or throughput?

Roles FAQ

Questions shops usually ask about role-aware software

A role-aware system should feel aware of the human structure inside the shop, not just the records.

1Why dedicate a page to roles?

Because role-specific relevance is a major part of the product's credibility. Serious shop software should acknowledge that different people need different views of the same work.

2What makes role-aware software believable?

Grounded and practical. It reads like Home Base understands the day-to-day pressure points behind each seat in the shop.

3Does every role need equal depth here?

No. Owners, service writers, and managers usually feel the buying pressure first, but the rest of the shop still needs a clean seat inside the system.