My progress
Menu

Digital Automation · Focus area 3: APIs, webhooks and RevOps

DA8: RevOps foundations

Goal: see how automation joins marketing, sales, service and accounts into one revenue process: what Revenue Operations (RevOps) means, the CRM as the shared record, capturing and routing leads quickly, the journey from lead to cash, and the numbers that show whether it's working.

You'll need: the CRM you built in Level 5 (or a free CRM account), the Sharma Textiles workflows from DA1–DA7, and a sheet for the numbers in Lesson 5.

Time: reading about 2 hours · practice (the Try it tasks) about 3 hours · assignment about 3 to 4 hours.

Where this is used: growing businesses often find that each team has its own tool and its own version of the truth. Sales says a deal is won, accounts hasn't been told, and the customer waits. RevOps specialists fix this with shared definitions, connected tools and automations across teams.

How it differs: a general automation builder speeds up one task at a time. RevOps looks at the whole path from first enquiry to payment and repeat purchase, and judges automations by their effect on revenue, speed and customer experience.

Lessons

  1. 1What RevOps isReading 15–25 minutes, plus practice✓
  2. 2The CRM as the shared recordReading 15–25 minutes, plus practice✓
  3. 3Capturing and routing leadsReading 15–25 minutes, plus practice✓
  4. 4From lead to cashReading 15–25 minutes, plus practice✓
  5. 5Measuring the revenue processReading 15–25 minutes, plus practice✓

🛠️Assignment: The Sharma Textiles revenue process

This joins the payment workflow, inbox router and CRM tidy-up into one RevOps design.

  1. Map the wholesale customer journey from enquiry to repeat order, marking every hand-off.
  2. Design the pipeline with stage meanings, required fields, owners, and which system owns each key field.
  3. Build lead capture and routing with deduplication, source, consent, an acknowledgement and an escalation after 30 minutes.
  4. Connect "Won" to the invoice, stock and warehouse steps, and match payments by order reference.
  5. Build a one-page funnel dashboard and write what you'd improve next.

Self-check before you finish:

✅Module check

Explain in a few sentences, in your own words:

How does automation help a business run its whole revenue process, not just single tasks?

Show a good answer

A good answer mentions: RevOps aligning marketing, sales, service and accounts around one process, data and numbers, with most losses at hand-offs; a CRM pipeline with clear stage meanings, required fields, owners, and one source of truth per field; lead capture with source, deduplication, consent, routing and fast first replies; lead-to-cash automations from "Won" to invoice, shipping and payment matching by reference; and a small set of numbers, such as stage conversion, speed to lead and days to collect, reviewed regularly, with attribution treated as a guide.

📚Official references

Official documentation and guidance for this module's topics, chosen on 2 November 2026. Tools, laws and standards change, so check the current version before you rely on a detail. If a link has moved, search the same site.

📝Module quiz

10 questions · 10 marks each · 100 marks in all · pass mark 70% · retry as often as you like ·

1. A boutique's ₹1,80,000 WhatsApp order went uninvoiced for two weeks: sales thought accounts knew, and accounts waited for sales. What's the RevOps fix?

Why each option is right or wrong

  • “Ask accounts to read the sales team's WhatsApp chats” (Incorrect): Reading chats is slow, unreliable and mixes personal and business messages.
  • “Remind salespeople in the next team meeting” (Incorrect): A reminder fades; the gap is in the process, not memory.
  • “Have the owner create every invoice personally” (Incorrect): That puts one more hand-off on the busiest person.
  • “Agree "Won" as the signal; automate the invoice step” is correct.

    The failure is at the hand-off. Agreeing that a deal moved to "Won" means "invoice now", and automating the invoice draft and a message to accounts, makes the hand-off happen every time without anyone remembering.

    • Agree first: stage meaning and owners.
    • Then build: the trigger on stage change.

📖 Revise: Lesson 1: What RevOps is

Question ID sp-digital-automation-08-q1 · Report a mistake in this question
2. Two salespeople use the "Quote sent" stage differently, and the pipeline value looks about twice the reality. What should you do first?

Why each option is right or wrong

  • “Halve the reported pipeline value” (Incorrect): A guessed correction hides the problem and stays wrong.
  • “Remove the "Quote sent" stage” (Incorrect): The stage is useful; it needs a clear meaning.
  • “Build a more detailed dashboard” (Incorrect): A dashboard on inconsistent data is still wrong.
  • “Agree an exit rule and require the quote file at that stage” is correct.

    The numbers are wrong because the stage means different things to different people. A written exit rule ("written quote sent") with a required quote file makes the stage consistent, so pipeline value and conversion rates become trustworthy.

    • Then: review stuck deals together.
    • Same for: every stage in the pipeline.

📖 Revise: Lesson 2: The CRM as the shared record

Question ID sp-digital-automation-08-q2 · Report a mistake in this question
3. The CRM and the accounts app both let staff edit invoice status, and an automation syncs both ways. Statuses keep flipping back. What's the cause and fix?

Why each option is right or wrong

  • “The sync runs too slowly; run it every minute” (Incorrect): Faster syncing makes the two systems overwrite each other faster.
  • “Turn off the sync and update both by hand” (Incorrect): That brings back manual work and mismatches.
  • “Add a second sync in the other direction” (Incorrect): There's already a two-way sync; that's the cause.
  • “Make accounts the owner; sync one way” is correct.

    With two editable copies syncing both ways, each change can be overwritten by the other side. Deciding that accounts owns invoice status, and copying it one way into the CRM, ends the conflict.

    • Write down: which system owns each key field.
    • CRM field: read-only for invoice status.

📖 Revise: Lesson 2: The CRM as the shared record

Question ID sp-digital-automation-08-q3 · Report a mistake in this question
4. Sales says Instagram ad leads are "poor quality". You find leads land in a sheet nobody checks at weekends, so Saturday leads get replies on Monday. What should you do?

Why each option is right or wrong

  • “Stop the ads, as sales suggests” (Incorrect): The leads haven't had a fair chance; the slow reply may be the real problem.
  • “Switch to a different ad platform” (Incorrect): The same slow follow-up would affect leads from any platform.
  • “Ask staff to check the sheet on Sundays” (Incorrect): It's a step forward, but still slow and easy to forget.
  • “Route leads into the CRM with an instant reply and weekend owner” is correct.

    Slow replies lower conversion whatever the source. Routing leads to an owner with an instant acknowledgement, then comparing conversion by response time, shows whether the leads or the follow-up were the issue.

    • Measure: speed to lead, before and after.
    • Decide later: on the ads, with fair data.

📖 Revise: Lesson 3: Capturing and routing leads

Question ID sp-digital-automation-08-q4 · Report a mistake in this question
5. A returning customer fills in an enquiry form and appears as a brand-new lead, assigned to a different salesperson from last time. What's missing?

Why each option is right or wrong

  • “A rule that blocks repeat customers from the form” (Incorrect): Repeat customers are valuable; they should be welcomed, not blocked.
  • “A weekly clean-up that merges duplicate contacts” (Incorrect): That helps afterwards, but the customer is already routed to the wrong person.
  • “A separate pipeline for repeat customers” (Incorrect): Without matching on entry, the system still can't tell they are repeat customers.
  • “Matching contacts on entry by phone or email” is correct.

    Deduplicating at capture, by cleaned phone (E.164) or email, attaches the enquiry to the existing contact. The routing can then send it to their previous owner, who knows their history.

    • Clean first: as in DA4.
    • Route: to the existing owner where one exists.

📖 Revise: Lesson 3: Capturing and routing leads

Question ID sp-digital-automation-08-q5 · Report a mistake in this question
6. A business wants to send WhatsApp offers to everyone in its CRM. Many contacts came from walk-in bills and never agreed to receive messages. What should the automation check?

Why each option is right or wrong

  • “That each phone number is valid” (Incorrect): Valid numbers matter, but don't show permission to message.
  • “That the message is short and polite” (Incorrect): Tone doesn't replace consent.
  • “That the contact bought within the last year” (Incorrect): A recent purchase isn't consent to marketing messages.
  • “That each contact opted in, and how” is correct.

    Marketing messages, and WhatsApp business messages especially, need the person's agreement. Recording consent and its source at capture, and sending offers only to contacts who opted in, respects customers and the platform's rules.

    • Others: invite them to opt in at the next purchase.
    • Record: date and source of consent.

📖 Revise: Lesson 3: Capturing and routing leads

Question ID sp-digital-automation-08-q6 · Report a mistake in this question
7. Accounts spends every Friday matching bank transfers to invoices, because customers write notes like "for sarees". What change does the most?

Why each option is right or wrong

  • “Hire a part-time person for Fridays” (Incorrect): That moves the work, without removing it.
  • “Ask customers to write clearer notes” (Incorrect): Some will, many won't; matching stays manual.
  • “Match payments by amount only” (Incorrect): Several invoices can share an amount, so payments would be matched wrongly.
  • “Payment links that carry the order reference” is correct.

    When the order reference travels with the payment, the payment webhook can match it to the invoice automatically. Manual matching shrinks to the few payments made without a reference.

    • Where supported: virtual account or UPI references.
    • Webhook: marks the invoice paid and updates the deal.

📖 Revise: Lesson 4: From lead to cash

Question ID sp-digital-automation-08-q7 · Report a mistake in this question
8. A deal moves to "Won" in the CRM. Which set of automated next steps fits lead-to-cash best?

Why each option is right or wrong

  • “Send the customer a thank-you message, nothing else” (Incorrect): A thank-you is nice but leaves the order, stock and invoice to be remembered by hand.
  • “Close the deal and archive the contact” (Incorrect): The customer relationship continues; archiving loses reorder chances.
  • “Email the whole company about the win” (Incorrect): Announcements don't start the work that needs doing.
  • “Invoice draft, stock reserved, warehouse task” is correct.

    "Won" is the hand-off from sales to fulfilment and accounts. Starting the invoice, reserving stock and telling the warehouse at once removes the days of waiting between teams.

    • Next: advance payment and shipment updates.
    • Owner: each task has a named person.

📖 Revise: Lesson 4: From lead to cash

Question ID sp-digital-automation-08-q8 · Report a mistake in this question
9. October's wholesale leads rose from 120 to 210, contact rate rose from 70% to 90%, and 60% of quoted deals still don't convert. Where should the team focus next?

Why each option is right or wrong

  • “Getting even more leads” (Incorrect): Leads already rose; the biggest leak is now after the quote.
  • “Contact rate, which is still not 100%” (Incorrect): 90% is strong; the larger loss is at the quote stage.
  • “Building a more colourful dashboard” (Incorrect): The numbers already show where to look.
  • “Why quoted deals don't convert” is correct.

    The funnel shows the largest drop after the quote. Looking at lost reasons, quote speed and pricing for those deals is where improvement is most likely.

    • Data: lost reasons recorded at "Lost".
    • Next: review ten lost quotes with sales.

📖 Revise: Lesson 5: Measuring the revenue process

Question ID sp-digital-automation-08-q9 · Report a mistake in this question
10. An owner wants to stop Instagram ads because few "Won" deals show source "Instagram". Several customers mention finding the shop on Instagram before messaging on WhatsApp. What's the sensible step?

Why each option is right or wrong

  • “Stop the ads now to save money” (Incorrect): The data may be missing Instagram's part, so the decision could cut a working channel.
  • “Double the ad budget, since customers mention it” (Incorrect): A few comments aren't enough evidence either way.
  • “Credit every WhatsApp sale to Instagram” (Incorrect): That swaps one wrong picture for another.
  • “Improve tracking, then review in two months” is correct.

    Customers often move between channels, so last-touch sources undercount Instagram. A "How did you hear about us?" field and UTM-tagged WhatsApp links give better data, and a review after two months gives a fairer decision.

    • Treat as a guide: attribution can't see everything.
    • Compare: cost per won deal by channel.

📖 Revise: Lesson 5: Measuring the revenue process

Question ID sp-digital-automation-08-q10 · Report a mistake in this question

ProLearners Assist