Team, roles and access

How many people in a plant actually need software access?

Usually more than owners first assume and fewer than a vendor would sell: sales officers, sales admin, works manager, stores and dispatch, quality, and the owner. Anyone who creates or changes a commitment needs a named login.

Talk to usAll answers

In short

Shared logins defeat the entire point. If three people use one account, nobody owns anything and the audit trail is worthless.

Start with the people on the governed line. Add the leadership view. Leave out anyone who only consumes reports; they can receive them.

Named users also make the pricing predictable, because the count only grows when the team does.

How pricing works

Who should approve a discount in a manufacturing business?

Set a band per role: the salesperson quotes the book, a sales head approves a defined slab below it, and anything deeper goes to the owner. Approval by phone call is not approval, because nothing survives the call.

What happens to your pipeline when a salesperson leaves?

If the relationships live in one person's phone, the pipeline leaves with them. If enquiries, contacts, quotations and next dates live on the company record, the handover takes an afternoon.

How do you get a shop floor team to actually use new software?

Give each role a single screen that shows only their work for today, and make recording faster than the workaround it replaces. Adoption fails when software asks the floor to serve the system instead of the other way round.

System of Marketing & Sales

Put enquiry to dispatch on one governed line.

Tell us how your plant sells today. We'll show you where the line breaks and what it takes to close it.

Talk to usBook a Demo