Bathtub Refinishing Website vs Field Service Software: What Should Own What?

Overview

A bathtub refinishing company can use one software platform for everything.

It can also use a strong website/front office plus a deeper field-service system.

The important question is not how many apps the company has.

It is whether staff know which system owns each fact.

The public website begins with:

The field system begins with:

Those are related, but they are not the same record.

• visual proof;
• service-area fit;
• customer-reported condition;
• photo enquiry;
• estimate request;
• ordinary contact history.
• verified surface;
• technical scope;
• estimate;
• technician;
• materials;
• field photos;
• completion;
• invoice;
• warranty case.

Let the website own acquisition

The public/front-office system should usually own:

That is where OneStudio fits most naturally.

Review current OneStudio features for live product scope.

• website;
• service pages;
• service-area pages;
• before-and-after portfolio;
• quote/photo enquiry;
• ordinary client/contact record;
• customer-facing estimate appointment when used;
• public analytics.

Let the field system own the accepted job

Once the project is accepted, the operational system may need to own:

A generic contact note should not become the refinishing job.

• property/job;
• actual surface;
• prior coating condition;
• repair/preparation scope;
• technical estimate;
• technician;
• production date;
• materials/product;
• operational photos;
• completion record;
• invoice;
• warranty case.

Keep customer-reported condition separate from verified condition

Customer says:

The tub is peeling.

That is useful intake context.

The technician may later determine a different technical condition or preparation requirement.

Preserve two concepts:

Keep photos separated by purpose

Keep the estimate where the job scope lives

A refinishing estimate may change after:

Use one authoritative estimate.

The public CRM can know that an estimate exists.

It does not need a second editable copy.

• photo review;
• site visit;
• prior-coating discovery;
• extra repair;
• additional surface;
• commercial unit count change.

Keep technician scheduling operational

A customer-facing estimate appointment can live in OneStudio when the business publishes a real appointment.

The production schedule is different.

It may depend on:

The field system should own the accepted production job.

• technician;
• travel;
• materials;
• job duration;
• access;
• property turnover schedule.

Keep materials and coating records specialist

Operational records may include:

Those facts are useful for field quality and warranty review.

They do not belong in marketing CRM by default.

• product/system;
• colour;
• batch or material reference where tracked;
• repair materials;
• actual usage.

Keep warranty cases linked to the original job

A warranty request should be traceable to:

That is richer than a generic support note.

OneStudio can receive the existing-customer enquiry.

The specialist/warranty workflow should own the technical decision.

• client;
• property;
• original job;
• surface;
• completion date;
• warranty policy;
• customer-reported issue;
• technical review;
• resolution.

Keep payment meanings distinct

Possible money objects include:

If OneStudio is used for a booking-linked payment where enabled, keep that meaning explicit.

The field/finance system should own the operational invoice if that is where actual job billing is calculated.

• estimate/consultation fee;
• booking deposit;
• production deposit;
• final invoice;
• warranty credit/refund.

Choose one explicit handoff event

Use a named transition such as:

Refinishing job accepted into operations

Possible triggers:

Choose one.

Before the event, OneStudio can own the public relationship.

After it, the field system can own the technical job.

• quote approved;
• deposit received;
• site review complete;
• production job created.

Use a source-of-truth matrix

Compare three practical stack patterns

A 26-point buyer test

1. The company controls its domain.
2. Marketing can update before-and-after proof quickly.
3. Service/location pages reflect real coverage.
4. Enquiry photo and public portfolio photo are separate concepts.
5. Customer-reported condition remains customer-reported.
6. Verified surface condition has one owner.
7. Handoff has one explicit trigger.
8. Stable source references exist where supported.
9. Accepted job has one owner.
10. Technical estimate has one owner.
11. Estimate revisions are explicit.
12. Production schedule has one owner.
13. Technician assignment has one owner.
14. Product/material record has one owner.
15. Field photos have one owner.
16. Completion date has one owner.
17. Operational invoice has one owner.
18. Website payment state is not confused with job accounting.
19. Warranty policy is operator-approved.
20. Warranty technical case has one owner.
21. Existing-customer support can trace the original job.
22. Generic lead nurture stops/changes after acceptance.
23. Stage-specific customer messages have one final owner.
24. Operational data does not leak into marketing exports.
25. Website URLs can survive a future field-system change.
26. Staff can explain the stack in one sentence.

Build around ownership, not feature count

The clean architecture is:

public website/front office → explicit job handoff → specialist field operations

OneStudio can own the first relationship.

The field system can own the verified job.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask