The Intelligent Decision Automation Playbook for Revenue, Operations and IT
Put the information you already have to work.
The next opportunity is not always another application. It may be a better way to connect the data, decisions, and workflows across the systems you already use. This playbook brings that approach into focus through three blueprints for customer experience, revenue creation, and IT automation.
Start with the decision, not the technology.
A signal in one system is useful only if the right person can put it into context and act on it. That is the thread running through this playbook: connecting information to the work it needs to inform.
Read it through the question you are responsible for answering.
CRO: Where could better information change the team's next move?
Use the revenue-creation blueprint to examine how customer and commercial information can inform action across teams. The useful question is where an opportunity or risk becomes visible, and who can act on it.
CMO: How does a marketing signal become useful to sales?
The customer-experience and revenue-creation blueprints connect customer data, engagement and downstream processes. Read them with the handoff in mind: what context would help sales decide whom to pursue and why?
CFO: What supports the revenue assumption?
Start with the discussion of revenue planning, then follow the information through the platform diagram. Use it to frame a conversation about the evidence behind an operating decision, rather than treating another report as the answer.
CIO: Where should the business logic live?
The platform diagram and IT blueprint show how integration, analytics and orchestration fit together. Use them to examine what stays in existing applications, what must work across them and where responsibility for change belongs.
RevOps: What happens after the team agrees on the number?
Follow the path from source data to insight, event and action. It is a useful way to examine where information stops at a report instead of reaching the person responsible for the next step.
Three blueprints. One connected view of the work.
The playbook brings integration, analytics and process orchestration together, then shows how that architecture applies to three business situations.
Customer experience
Follow a blueprint that brings customer and engagement data together, prepares it for analysis and feeds it into customer-facing processes.
Revenue creation
Explore how information across brands, channels and connected products can inform customer understanding and revenue decisions.
IT automation
See how project, task and robotic automation events can be connected across applications, rather than managed as separate activities.
Read the playbook
Start with the platform diagram on page 16, then explore the blueprints on pages 17, 19, and 21.
These are broader Put It Forward platform examples. They are not a statement of the scope or results of a Revenue Agent engagement.
Compare the scope of the solution, not just the feature list.
A workflow inside one application and a decision that depends on several systems are different design problems. Use this comparison to decide how much of the process needs to work together, then ask each provider to demonstrate that scope.
| Question | A task-level approach | A connected decision-and-workflow approach |
|---|---|---|
|
Where does the work begin?
|
With a defined task or trigger in a particular application.
|
With a business decision and the information needed from the systems involved.
|
|
What information is considered?
|
The inputs required to complete that task.
|
Relevant data brought together and prepared for analysis across the process.
|
|
What happens after an insight?
|
A person or a separate workflow may need to carry it forward.
|
The design connects the insight to a next step, an owner or a downstream event.
|
|
How are people involved?
|
People handle the task's approvals and exceptions.
|
Responsibilities and review points are considered across the full decision path.
|
|
How are changes managed?
|
Changes are evaluated against the local task.
|
Changes are also evaluated for their effect on sources, rules and downstream work.
|
|
How is value measured?
|
Completion time, effort or errors within the task.
|
Those measures plus the business outcome the connected process is intended to support.
|
|
What determines implementation effort?
|
The task, its application and its immediate dependencies.
|
The number and condition of the sources, decision logic, access requirements and operating responsibilities.
|
|
What should be demonstrated?
|
That the task runs correctly.
|
That the information, decision and next step work together, including review and exception handling.
|
These are design scopes, not ratings of named vendors. The playbook illustrates the connected approach; the capabilities and configuration required for your use case should be demonstrated before you commit.
How the Revenue Agent works
Revenue Agent brings this approach to a specific commercial question: which events in the data you already have deserve attention?
It uses techniques from signal intelligence and algorithmic trading to identify meaningful revenue events amid large volumes of signals. It brings those events into context, with recommended next steps for the revenue team.
The playbook explains the broader approach to connecting data, decisions and workflows. A Revenue Agent discussion takes that into your use case: the sources involved, the decision to support and what your team should be able to do with the result.
Explore the assumptions behind an automation business case.
Use the calculator to explore a scenario, not to predict a result. Start with your own baseline for effort and errors, and make each improvement assumption explicit.
Illustrative estimate only. The result depends on the inputs and calculation assumptions; it is not a Revenue Agent outcome, a price quotation or a commitment to savings.
What Others Say About Put It Forward
These comments describe customers' experience with the broader Put It Forward platform. They are not a forecast of an engagement's results.
Director of Program Management
“Having our global teams all working from the same page is critical to our success. Put It Forward exceeded way beyond where others died.”
Director of Operations and Technology
“What you just did for our teams' productivity and how we work was magic - you guys are rock stars, I’m truly blown away”
CTO
“Put It Forward takes us where no others could - we struggled for years with an enterprise data story - this solved it across the board”
Marketing Platform Technologist
“For me when our internal teams tried to replicate the Put It Forward technology that was when the pin dropped … these are really smart people”
FAQs about the playbook and what comes next
It is a broader guide to connecting data, analytics and workflows across revenue, operations and IT. Use it to understand the approach and frame a use case; a Revenue Agent engagement has its own agreed scope, deliverables and evaluation criteria.
The playbook shows how information and processes can work across existing applications. For a specific use case, the next step is to confirm the source systems, available interfaces, access requirements, data quality, and actions involved.
Choose one decision or workflow where better information could change what happens next. Identify who owns it, which systems provide the context, and what a useful result would look like before expanding the scope.
They can help structure the evaluation, but neither establishes your return. A credible business case needs your baseline, full costs, an agreed observation period and evidence of the change achieved.
Review the proposed data access, processing, permissions, operating responsibilities and applicable security and privacy requirements for the specific deployment. The playbook is not a security assessment or a certification statement.
Confirm the workflow, source systems, responsibilities, delivery milestones, support arrangements and commercial terms. Reading the guide or requesting a discussion does not commit you to an implementation.
No. You can read the guide on this page or open the PDF directly. If you want to discuss a particular workflow, use the optional form below.