Internal Brief for Mercilus

Sales Operations Framework for Sprint Internet

This document outlines the operating framework I propose for Sprint Internet’s sales function. It is intended to support stronger visibility, clearer governance, more consistent execution, and a more dependable path from opportunity development to implementation and delivery.

My objective is to create a structure that helps the business scale without losing control, discipline, or customer focus.

Executive Context

I see the current sales operation as strong in intent but difficult to scale with consistency. The business is moving opportunities through a chain of conversations, emails, proposals, technical reviews, and approvals, but the process is not yet structured enough to give us a reliable view of what is happening at each moment.

That creates avoidable friction. I lose time chasing updates, the team can work from incomplete context, and leadership does not always receive a clear picture of progress, risk, or forecast confidence until the issue is already visible. I want to reduce that friction by building a system that gives us structure without slowing the sales motion down.

My aim is not just to digitize activity. I want to create a disciplined operating model where the team can move quickly, decisions can be made with confidence, and customer delivery can begin with better preparation and fewer surprises.

Current Reality Sales activity is moving, but visibility is fragmented and accountability is not always clear.
Target State One structured process with shared visibility, clearer accountability, and controlled handoffs.
Operational Challenge Important details are often distributed across multiple channels, creating delays and avoidable rework.
Desired Outcome A clearer, more controlled sales engine that supports growth and protects delivery quality.

What I Want the System to Achieve

  • Create one visible path for every opportunity from first contact to implementation.
  • Reduce manual follow-up and make deal progress easier to track.
  • Improve coordination between sales, commercial, and technical teams.
  • Give me a clearer approval structure for pricing, discounts, and service terms.
  • Provide leadership with better visibility into pipeline health, forecast confidence, and performance.
  • Protect the customer experience by ensuring each handoff carries the right information at the right time.
Process Visibility Every opportunity is visible from creation through close and handover.
Operational Discipline The team follows the same workflow with fewer gaps and fewer missed steps.
Cross-Functional Coordination Sales, commercial, and technical teams work from the same information base.
Cleaner Execution Delivery begins with better preparation and fewer handoff issues.

Core Process Flow

1. Lead Qualification
→
2. Requirements Review
→
3. Proposal and Negotiation
→
4. Approval and Close
→
5. Handover and Delivery

I want each stage to be visible, dated, and linked to the relevant customer context, commercial position, and technical requirement. That makes handoffs more reliable and reduces the risk of information being lost between teams.

Opportunity Lifecycle Prospecting, qualification, requirements gathering, proposal submission, approval, contract close, handover, and implementation support.
Key Control Points Commercial review, technical validation, customer approval, and implementation readiness before delivery begins.

Governance and Control

I want the system to include a structured governance layer for commercial and operational control. Standard pricing and standard service terms can be handled through defined rules, while non-standard requests can be routed for review and approval without slowing down the broader process.

This gives the business control over margin, quality, and consistency while still allowing the team to work with speed and confidence. It also creates a more dependable framework for decision-making when a deal becomes more complex.

Sales Strategy Playbooks, battlecards, templates, and clear commercial guidance that support consistent execution.
Account Intelligence Customer profiles, decision-makers, service history, contract timing, and renewal context in one place.
Proposal and Approval Structured review, pricing control, and approval workflows with clear responsibility.
Delivery and Handover Secure transfer of technical requirements, implementation details, and operational expectations.

Customer and Account Management

I also want this system to support stronger account management. For enterprise opportunities, I need more than a simple pipeline record. I need a clear view of the account, the stakeholders involved, the technical environment, the commercial history, and the likely next steps.

That means every major account should have a structured profile that helps the team understand the customer’s priorities, who is influencing the decision, and what information is already known before the next conversation begins.

Account Profile Customer strategy, priorities, contacts, and commercial history in a single view.
Decision Insight Stakeholder influence, service requirements, and known objections highlighted clearly.
Delivery Context Technical footprint, support expectations, and implementation narrative preserved over time.
Relationship Continuity Multiple reps can step in without losing the account history or context.

Team Structure and Coverage

The current sales team includes a mix of administration, customer experience, and revenue-facing roles. A structured operating system will help this team work with better consistency, clearer accountability, and more reliable handoffs across the customer journey.

Administration and Support Suzzette Kahumuza – Sales Administration and Documentation.
Customer Experience Angel Michelle – Customer Experience and Relations.
Sales Executives Shadia Namatovu, Moses Okwalingal, Joy Egazu, Kisanet, and Niyatt.
Enterprise Growth Martha Mildred Ninsiima – Enterprise Business Sales Executive.

Forecasting and Performance

I want the system to support more disciplined forecasting. Instead of relying on late updates and informal reporting, I want leadership to see movement across the pipeline, track conversion progress, and understand where risk or delay is emerging earlier.

This creates a stronger basis for coaching, decision-making, and performance review. It also helps the business move from reactive reporting to proactive management rather than waiting until the end of the month to discover a problem.

Forecast Input Pipeline movement, stage progression, historical conversion, and current deal confidence.
Forecast Output Revenue expectation, shortfall indicators, and action points for the next reporting cycle.

Expected Impact

If I implement this well, I expect Sprint Internet to gain a more consistent sales operation: clearer account visibility, stronger cross-team coordination, better control of commercial decisions, and a more reliable path from opportunity to delivery.

The value will not only be operational. It will also be strategic. I want the business to be better prepared for growth, with a system that supports execution without sacrificing control or customer experience.

Before Fragmented updates, delayed visibility, manual follow-up, and inconsistent handoffs.
After Shared visibility, consistent governance, better forecasting, and stronger delivery readiness.
In practical terms, my aim is to make the sales function easier to manage, easier to scale, and easier to govern without losing speed, clarity, or customer focus.

Example: Account Profile — Wamuco Motors

Below is a practical example of how an account profile could look for Wamuco Motors, using a simple structure that supports relationship management and business planning.

Account Summary Wamuco Motors is a growing motor dealership with interest in reliable internet connectivity for administration, sales, customer service, and operations.
Key Contacts Managing Director, Operations Manager, Finance Lead, and IT/Facilities contact.
Business Need Stable internet, backup connectivity, and dependable support for daily operations.
Current Status Existing connection in place, but service reliability and support response need improvement.
Commercial Notes Price sensitivity is present, but uptime and service quality are critical to the decision.
Next Action Schedule a site review, confirm current package fit, and present upgrade or backup options.

Example: Product Document — Internet DIA and Home Connections

This example shows how a product document can present the core value, technical fit, and commercial positioning for Internet DIA and Home Connections.

Product Overview Internet DIA is designed for business users who need stable, high-performance connectivity; Home Connections serve residential users looking for dependable everyday access.
Key Benefits Reliable uptime, clear service levels, flexible packages, and support for both professional and household use.
Internet DIA Suitable for offices, branches, digital operations, and business-critical applications.
Home Connections Suitable for households, streaming, remote work, browsing, and general family use.
Commercial Positioning Position DIA around performance and business continuity; position Home Connections around convenience, value, and consistency.
Sales Message Match the package to the customer’s use case, expected reliability, and budget.

Example: Governance Document

A governance document should define how the sales function is controlled, reviewed, and improved over time.

Purpose To ensure consistent handling of opportunities, pricing approvals, customer communications, and handovers.
Scope Covers the sales process, commercial approvals, service commitments, escalation points, and reporting expectations.
Approval Rules Standard deals follow a defined path; exceptions require review and sign-off.
Review Cadence Weekly pipeline review, monthly performance review, and periodic governance checks.
Accountability Sales, customer experience, and operations each have defined responsibilities in the journey.
Continuous Improvement Feedback from customers and the team is used to refine the process and improve execution.

Example: Customer Feedback Form

This is a simple example of a customer feedback form that can be used to capture service experience, satisfaction, and improvement areas.

Customer Details Name, company, contact number, account type, and preferred contact method.
Service Rating Rate installation experience, support responsiveness, connection stability, and overall satisfaction.
Open Feedback What went well, what did not, and what the customer would like improved.
Follow-Up Confirm whether the customer wants a call-back, escalation, or product recommendation.

Example: Sales Calendar for the Month

A monthly sales calendar helps the team plan activity, maintain focus, and ensure that key account actions are not missed.

Week 1 Prospecting calls, new lead follow-up, and account research.
Week 2 Customer visits, proposal submissions, and technical qualification meetings.
Week 3 Follow-up calls, negotiation review, and approval tracking.
Week 4 Close-out review, pipeline update, forecasting, and next-month planning.

Example: Appraisal and Performance Document

Below is a simple example of a performance document that can support regular review and development conversations.

Employee Name Sales Executive / Customer Experience Officer.
Review Period Monthly or quarterly performance review.
Performance Summary Strong relationship building, consistent customer follow-up, and good attention to detail.
Development Areas Improve proposal turnaround time and strengthen cross-team coordination.
Goals Increase conversion rate, improve customer response time, and maintain accurate pipeline reporting.
Manager Feedback Continue strong execution while improving consistency in planning and communication.

Recommended Next Steps

I recommend that we begin by validating the workflow with the sales team, confirming the key approval points, and defining the information that must travel with each opportunity. From there, I can turn this brief into a practical implementation plan with clear ownership, milestones, and reporting expectations.

The immediate goal is to move from concept to a working framework that reflects how Sprint Internet actually sells, coordinates, and delivers.