Skip to content
GullySales

Computer stores · Sales activity management

I know what my salespeople sold last month, but not what they did to get there.

Sales activity management sets out what each salesperson is expected to do in a working day, records it in one simple place, and checks it against orders. GullySales writes the activity plan with you, sets up the log in your CRM or a shared sheet, and builds the manager's check.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Computer repair shops: show a real physical business scene illustrating Device intake and condition check. Record serial, make, fault described, accessories, passwords, scratches and photos, and print a tag and a customer receipt.

Start with the buying decision

Which record or handover breaks between the enquiry and its outcome?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Computer stores

Start with the decisions in your own enquiry records.

Trace a real enquiry across the people and systems involved. Record missing information, duplicate work, and the decision that is still waiting for an owner.

How people choose in this industry

Offices choose a computer supplier on whether the quote is clear, whether the machines are installed and set up rather than dropped at the door, and whether someone answers when a system fails. Price matters, but a purchaser who has been burned by a supplier who vanished will pay more for a name they can call.

Home buyers and students come for a build that fits a purpose: a school-work machine, a video-editing desktop or a gaming build. They compare parts lists, ask which brand of power supply is safe and want the shop to explain the choices rather than just sell the dearest set.

The decision before implementation

Define the process and access permissions before changing software settings or adding automation.

Existing industry priorities to review

  • Written quotes with options for offices
  • Configuration pages for home, office and studio systems
  • Annual maintenance contracts for office customers
  • Replacement cycle reminders for offices
  • School and institution quotation routines

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

Our best customers are offices we only hear from when something breaks

We have no plan to visit, remind or offer them upgrades before they call another supplier.

Output to assess: Activity definitions

Review whether “Activity definitions” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

Office enquiries come by phone and are never quoted in writing

A purchase manager asks for a rate, gets a number over the call and compares it with a written quote from a rival.

Output to assess: Activity definitions

Review whether “Activity definitions” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

The problem

What sales activity management is meant to address.

  • “I cannot tell a quiet month from a lazy one”

    Orders fell, but nobody can say whether visits fell too. Without a record of activity, every explanation from the team sounds equally likely.

  • “Every rep reports in a different way”

    One sends a voice note, another fills a notebook, a third updates the CRM once a week. The manager cannot compare them or add them up.

  • “Quotations go out and nobody calls back”

    The rep sends a price and moves to the next visit. The buyer waits for a call, then takes the quotation from the supplier who rang.

  • “The team does the easy activity”

    Reps ring old friendly customers and skip new accounts, because both count as one call. The log needs to show the difference.

Who it is for

Check your operating model against the scope.

  • Owners of dealer, distributor and manufacturing sales teams who see only the month-end order total
  • Clinics, schools and showrooms where front-desk staff handle enquiry calls and walk-ins
  • Service firms whose proposals go out and are never chased
  • Sales managers who inherited a team with no written expectations
  • Field teams that report by WhatsApp message, with nothing a manager can add up

Before you decide

When this may not be the right fit.

  • A business that wants to track staff movement or location rather than selling work
  • A team of one, where the owner already knows each day's calls and visits
  • An owner looking for sales targets set for them: targets come from your own history and are agreed with you

What we do

Agree the outputs before work begins.

These are the sales activity management deliverables available for computer stores. Your written scope identifies the included work and responsibilities.

  1. Role activity plan

    A one-page document per role listing the calls, visits, quotations and follow-ups expected. You approve the plan, and the rep who will follow it reads it before it starts.

  2. Activity log

    A set of CRM fields, or a shared sheet where no CRM exists, that records the date, customer, type of activity, outcome and next step. It is built to be filled in under two minutes after a call or visit.

  3. Activity definitions

    Written rules for what counts as a call, a visit, a quotation sent and a follow-up done. A missed call, a WhatsApp reminder and a repeat visit to the same site are each ruled on.

  4. Manager check sheet

    A short list the sales manager works through on the log: planned against done, follow-ups that have fallen due, quotations with no contact since. The owner sets when it is run.

  5. Activity-to-outcome view

    The log set beside enquiries, quotations and orders, so you can see which activity comes before orders and which fills the log without moving anything.

  6. Rep briefing note

    A plain explanation for the team of what is recorded, who reads it and how it is used. It states what the log is not used for.

  7. Plan revision record

    A dated note of each change to the plan and the reason, so the next owner or manager can see why a role looks the way it does.

How the result is measured

  • Planned activity against activity logged, per role
  • Quotations with a follow-up recorded after sending
  • Follow-ups due and follow-ups completed
  • New-account contacts compared with repeat-customer contacts
  • Log entries completed on the day of the activity
  • Activity types that preceded recorded orders

Recorded as a baseline before work starts, so every later report has an honest comparison.

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Quote requests by source
  • Written quotes sent against orders won
  • Systems per order
  • AMCs signed and renewed
  • Repeat orders from offices
  • Reply time to quote requests

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Sales productivity improvement
Choose sales productivity improvement when you suspect avoidable work, slow approvals or clumsy forms are keeping reps from buyers. Choose sales activity management when the gap is that nobody has agreed what each person should do from one working period to the next or how it is recorded.
Sales metrics and KPI development
Choose sales metrics and KPI development when the argument is about which numbers matter and how they are calculated. Choose sales activity management when the numbers are fine but the behaviours behind them, such as calls and visits, are undefined and unrecorded.
Sales review management
Choose sales review management when the meetings themselves need an agenda, a sheet and an action tracker. Choose sales activity management when the manager attends reviews with nothing reliable to look at, because the activity log and the plan behind it do not exist.

A sample of the output

A role activity plan states what a salesperson does, how it is logged and what the manager checks.

This is an extract for an inside salesperson at a furniture retailer. Each row is one expected activity, with the definition that stops it being counted loosely and the check a manager makes.

Illustrative example, not client data. Yours is built from your own records.
ActivityWhat countsWhere it is loggedManager check
Outbound callA conversation with a named buyer about a live enquiryCRM call entry with outcomeOutcomes match the notes on the enquiry
Showroom follow-upA message or call to a visitor who left detailsCRM note linked to the visitVisitors with details have a recorded follow-up
Quotation sentA priced document sent to a named buyerQuotation registerEvery quotation has a next step and a date
Quotation chaseA contact about a quotation already sentCRM task marked doneChase notes show what the buyer said
Order confirmationBuyer acceptance matched to a purchase orderAccepted order logOrders link back to earlier activities

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A description of a normal working shift
The activity plan has to fit the way each role actually works. A walk-through from the person doing the job is enough. Without it, the plan describes an ideal day, and the team treats the log as extra paperwork.
A decision on where the log lives
The log sits in your CRM or a shared sheet, and one place must be chosen. Either is acceptable. If the choice is left open, activity ends up in several places and the manager's check has nothing complete to read.
A manager who will do the checks
The manager check only works if a named person has time to carry it out. It does not need to be long. When nobody owns it, the log fills up without being read and the team stops entering data.
Agreement on what counts as activity
Definitions settle arguments about whether a message or a missed call counts. You decide the rules with your sales head. Without that agreement, two people log the same effort differently and the activity view cannot be compared across the team.
Recent order records
Linking activity to orders needs some completed orders to compare against. Exports or paper records are acceptable if they name the salesperson. Without them, the plan can be written but its link to results cannot be checked.

How it works

How sales activity management runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Role walk-through

    We sit with you and the sales manager and list what each role does in a working day. You decide which activities belong in the plan.

  2. 2

    Plan and definitions sign-off

    We draft the role plans and the counting rules. You approve them before any rep sees them.

  3. 3

    Log build

    We set up the log in your CRM, or in a shared sheet. A rep from each role tries it on real calls before the rest of the team uses it.

  4. 4

    Team briefing

    The briefing note is explained to the team with you present. Questions about how the log will be used are answered before recording begins.

  5. 5

    First manager checks

    We run the check sheet with the sales manager on the first entries. Gaps in the log are separated from gaps in selling.

  6. 6

    Linking to orders

    Once the log has enough entries, we set it beside your orders and show you which activities came before them. You decide what to change in the plan.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Role activity plan

    Check that each proposed priority has a stated reason, a responsible person, and a next decision. Record any unsupported assumption before the owner approves the plan.

  • Activity log

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Activity definitions

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Manager check sheet

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Activity-to-outcome view

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Rep briefing note

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Plan revision record

    Check that each proposed priority has a stated reason, a responsible person, and a next decision. Record any unsupported assumption before the owner approves the plan.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is sales activity management scoped for computer stores?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Define the process and access permissions before changing software settings or adding automation.
Do we need a CRM to start?
No. A shared sheet with fixed columns works for a small team. If you already use a CRM, the log is built inside it so reps enter things once. Choosing or installing a CRM is separate work, covered under CRM adoption and training.
Will reps feel they are being watched?
They can, so the briefing note says what is recorded and what the log is not for. The plan covers selling work. It does not track location or personal time.
Can you tell us the number of calls a rep should make?
Not before looking at your records. A figure borrowed from another business means nothing for yours. The plan starts from what your team does now and what your own orders show, and you set the final expectations.
How is this different from pipeline management?
Pipeline management follows each deal through its stages. Sales activity management follows the person: what they were expected to do and what they did. The two share data, and the sales review is where they meet.
What about fees and how long it takes?
Scope, fee and term are set in writing after we read your requirements brief and speak with you. No figure or duration is quoted before that.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.