Feature · Business Process Automation Example

Eight business process automation examples, worked end to end.

Eight concrete processes that revenue teams run on Strkr today, each walked through from the trigger that fires the flow to the audit record that closes it. Discount approvals, Closed Won onboarding, ninety-day renewal motion, legal clause routing, QBR cadence, sales-to-CS handoff, executive escalation, partner co-sell. Specific inputs, specific steps, specific outcomes.

Start free trial See pricing

Deal approval worked example

Discount over twenty percent, three tiers, forty-eight-hour SLA.

The first worked example is the single most common revenue BPA pattern: a discount approval chain with three tiers and a defined SLA. The example is specific. The rep is Marcus. The deal is sixty thousand dollars. The requested discount is twenty-two percent. The product line is Platform. The region is North America segment two. The output at the end is a signed quote, an audit record, and a deal moved to the next stage without a Slack thread.

The trigger

Rep saves the deal with a discount above threshold.

Marcus applies a twenty-two percent discount on the sixty thousand dollar Platform deal and saves. The process fires on the save event with the condition set: discount percent greater than fifteen, deal amount greater than twenty-five thousand, segment not in strategic. All three conditions resolve true. The deal state changes to Discount Pending Manager Approval. A banner appears on the deal, visible to Marcus and his manager.

Tier one approver

Routes to the regional sales manager with context.

The first approval routes to Marcus's regional sales manager, Priya. Priya receives the request in her approval queue, in Slack, and in email. The request opens on the deal page itself with Marcus's notes attached, the exception context visible, the deal structure in one view, and three buttons: approve, request changes, reject. Priya reads, approves, adds a note about the strategic cover value, and the process advances.

Tier two approver

Director reviews with margin analysis attached.

The system routes to the regional director, Chen, with Priya's approval note already attached. Chen opens the request and sees the exception context, the margin analysis pulled from the deal's product line and discount combination, and the account history. Chen approves on the forty-ninth minute, adds a note confirming the margin stays above the floor at twenty-two percent, and the process advances to the VP.

Tier three approver

VP approves from a phone, the chain closes.

The system routes to the VP, Amara, with the full chain attached. Amara is at a conference. She opens the Slack message on her phone, reviews the summary, taps approve, and the chain closes. Amara's approval signs off against the policy version in effect at the request time, which the system records on the audit trail along with the device and channel of her approval.

Side effects

Discount applies, quote regenerates, Marcus gets a note.

The process fires five side effects on approval. The discount applies to the deal line items. The quote regenerates with the new numbers against the current template. The regenerated quote PDF attaches to the deal. The primary contact receives the updated quote by email with a configurable cover note. Marcus receives a notification that the deal is unlocked. The timeline shows the full chain with notes from every approver.

SLA tracking

Forty-eight hour clock elapses on each tier.

Each tier of the chain has a forty-eight hour SLA from the moment the request lands on the approver's queue. The SLA pauses on weekends and holidays. The system elapses the clock in real time and surfaces the current tier's remaining hours on the deal page. If a tier breaches, auto-escalation fires to the next level with the breach reason captured on the audit trail. In the Marcus example, no tier breached because Priya closed in forty-five minutes, Chen in forty-nine, and Amara in six.

Audit record

Every approval decision captured for the Q4 review.

The audit record for this deal captures the request, each approval tier, each note, the policy version applied, the device and channel of each approval, the elapsed time, and the final discount applied. When the Q4 SOC 2 Type II review asks about discount governance for North America deals above twenty percent, the controller pulls the saved view and the audit records appear with full context. No reconstruction of a Slack thread, no screenshot of a chat archive.

Closed Won onboarding example

Five actions, zero manual tasks, within sixty minutes.

The second worked example is the onboarding motion that fires when a deal moves to Closed Won. The example is the deal Marcus closed in the first example. Platform tier, sixty thousand dollars, North America segment two. When the deal state advances to Closed Won, the onboarding BPA fires with five downstream actions. Every new customer gets the same first touch within sixty minutes of close, regardless of which AE closed the deal.

The trigger

Deal state advances to Closed Won.

Marcus's deal state advances from Pending Countersignature to Closed Won when the signed order form webhook returns from the e-sign provider. The onboarding process fires on the state transition event with the deal context, the account context, and the signed order form attached. The trigger is specific to the Closed Won state so the process does not misfire on manual stage changes that reverse the next day.

Create the project

Customer project with the solution scope attached.

The first action creates the customer project in the Projects module with the solution scope pulled from the deal's scope section. The project carries the deal ID as a cross-reference, the product line as the project template selector, and the start date as the signed order form execution date. The project appears on the account page as the first implementation record and lands in the implementation team's queue.

Assign the lead

Implementation lead picked by segment and region.

The second action assigns an implementation lead using the current staffing matrix: North America segment two deals route to the regional implementation pool with the current capacity-weighted assignment rule. The assignment produces a lead, Nolan, whose load is the lowest in the pool. The assignment lands on the project, the lead receives a notification, and the account gets a name instead of a generic team mailbox.

Generate the kickoff deck

Deck pulled from deal context with the AE notes merged.

The third action generates the kickoff deck from the deal context: account name, primary contact, product line, use case summary, success criteria, and Marcus's deal notes. The deck template renders in seven slides, lands on the project, and is ready for Nolan to review and personalize before the kickoff call. The slide that used to take Nolan an hour on the Friday before the call takes four minutes.

Book the kickoff

Thirty-minute meeting on AE and CS calendars.

The fourth action books a thirty-minute kickoff call on Marcus's calendar and Nolan's calendar for the next business day during the account's business hours. The booking uses the shared calendar availability lookup and respects the account's timezone from the account record. The customer primary contact receives the calendar invite with the agenda pre-populated. No scheduling chase, no back-and-forth email.

Send the welcome

Welcome email with the pre-work checklist.

The fifth action sends the welcome email to the customer primary contact with the pre-work checklist for the kickoff call. The email renders from the welcome template with the account name, the product line context, and the kickoff call details merged in. The checklist points to the three artifacts the customer needs to assemble: data access confirmation, integration contact, and executive sponsor.

Timing summary

Sixty minutes from Closed Won to welcome email landing.

The full chain fires inside sixty minutes of the Closed Won state transition. In the Marcus example, the signed order form returned at 2:14 p.m. local and the welcome email landed in the customer inbox at 2:47 p.m. The AE did not open the project, the implementation lead did not open the deal, and the customer received a consistent first touch regardless of day of week or which AE closed the deal.

Audit record

Onboarding chain logged for the handoff review.

The audit record captures every action in the chain with timestamps, the data that fired each action, the user who received each notification, and the final state of the project. Teams running a monthly handoff review open the saved view and inspect the chain to confirm every new customer received the full motion. Variances flag for a conversation with the ops lead.

Renewal and legal routing examples

Two more worked flows that revenue teams run every week.

Two more worked examples that cover the next most common revenue BPA patterns: the ninety-day renewal motion that fires without a human and the contract routing flow that sends non-standard clauses to legal while sending the standard ones directly to the deal desk. Both examples carry the same shape: specific trigger, defined steps, named approvers, measurable output, and an audit record at the end.

Renewal trigger

Ninety days before contract end, process fires.

For every active contract, the system checks each night whether the contract end date is exactly ninety days out. On the day the condition becomes true, the renewal process fires. In the example, the account is Riverside Logistics, the current ARR is forty-eight thousand, the contract end date is one hundred and ten days from today, which means the ninety-day flag fires in twenty days. The CSM, Hana, is unaware until the automation runs.

Renewal opportunity

Create the renewal opp with the current ARR and tier.

The first renewal action creates a renewal opportunity in the CRM with the current ARR carried forward and the pricing tier mapped against the latest published rate card. The opportunity carries the parent contract as a cross-reference, the account owner as the primary rep, and the renewal date as the expected close date. The opportunity lands on Hana's forecast with the renewal segmentation applied automatically.

At-risk scoring

Health signals from usage and support fire the score.

The second renewal action calculates the at-risk score from the account's usage data, support ticket volume, and executive engagement signals across the last two quarters. The Riverside account posts a green score because usage is stable, support volume is low, and the executive sponsor has engaged in two QBRs. The score pins to the renewal opportunity and informs the renewal play Hana runs next.

Renewal one-pager

Document generated from account data, ready for Hana.

The third renewal action generates the renewal one-pager with the executive summary pre-populated from account usage, QBR outcomes, and the current ARR. The one-pager lands on the account page ready for Hana's review. The template that used to take Hana an hour the Friday before the renewal conversation takes her six minutes to review and personalize.

Legal routing trigger

Deal moves to Contract stage with the clause inspection.

A separate flow handles contract routing when any deal moves to the Contract stage. The process inspects the contract type and the flagged exception fields on the deal. In the example, the deal has a standard MSA, a standard DPA, but a custom data residency clause the rep selected on the deal. The custom clause triggers the legal routing branch.

Standard contract routing

Standard clauses go to the deal desk for countersignature.

For deals with every clause set to standard, the process routes directly to the deal desk for countersignature without a legal review step. The deal desk receives the request with the full contract rendered from the template, the pricing table attached, and the signatory block populated. The deal desk countersigns, the signed artifact returns to the deal, and the deal advances to Signed in under four hours.

Non-standard contract routing

Legal review on the exception, with full context.

For the Riverside example with the custom data residency clause, the process routes to legal first with the exception highlighted. Legal receives the request on the deal page with the custom clause outlined in red, the rep's justification note attached, and the historical data residency positions available for reference. Legal reviews, approves with a slight edit to the clause wording, and the process continues to the deal desk for countersignature.

Audit outputs

Both chains close with the audit records intact.

Both the renewal and the legal routing examples close with audit records that capture every step, every approver, every note, and every clause version in force at the time. For the Q2 audit review, the controller filters the audit log by date range and process type and exports the matching records. The pattern replaces a quarterly scramble to reconstruct governance evidence from Slack and email.

Four more examples at a glance

QBR cadence, handoffs, escalations, and partner co-sell.

Four more worked examples that revenue teams run on Strkr today, each with a trigger, defined steps, and audit output. The level of detail is the same as the first two sections: these are not aspirational diagrams, they are the flows that show up in the first ninety days of real deployments across revenue teams in SaaS, services, and B2B product organizations.

QBR cadence

Strategic accounts hit QBR every ninety days.

A nightly process checks each strategic-tier account against the last QBR date. When the gap crosses ninety days, the process creates the QBR task, pulls the account metrics into the standard QBR template, pings the CSM to schedule, and surfaces the QBR on the account page with the deadline visible. The CSM receives the fully-prepared artifact instead of starting from a blank slide deck.

Sales-to-CS handoff

Closed Won fires the handoff beyond onboarding.

After the Closed Won onboarding chain fires, a second process handles the ongoing sales-to-CS handoff: assign the CSM by segment and region, share the deal context, open the shared Slack channel between the AE and the CSM, log the handoff on the account timeline, and schedule the thirty-day check-in on both calendars. The CSM owns the account from day one with the full context attached.

Executive escalation

Red health score for two weeks fires the escalation.

When a strategic account posts a red health score for two consecutive weekly measurements, the escalation process fires. The chain creates the escalation record, pings the account owner's VP with the context, schedules a thirty-minute internal review on the next available slot, and tags the customer leadership channel in Slack. The VP joins the review with the context already assembled rather than cold.

Partner co-sell

Partner registers a deal, the motion starts.

When a partner registers a deal through the portal, the co-sell process fires: create the opportunity with the partner source attached, route it to the right territory AE, open the shared partner-AE Slack channel, generate the co-sell plan template, and set the first partner sync for the following Tuesday. Partner deals follow a defined motion from day one instead of starting as an email in the channel manager's inbox.

Policy version pinning

Every example references the policy in force at the time.

Across all eight examples, the audit record pins the policy version in effect at the time of the decision. When the discount threshold changes in Q3 or the renewal lead time shifts to one-twenty days, historical records reference the earlier version. Nothing retroactively looks wrong because the policy evolved, and nothing requires a human to remember which version was in force on a date months ago.

Branching patterns

Each example uses the same approval and routing primitives.

Every example reuses the same core primitives: trigger blocks, condition blocks, approval blocks with delegation, record update blocks, document generation blocks, notification blocks, and the audit log. The patterns compose rather than duplicate. A team that builds the discount approval chain in week one can build the renewal motion in week two with ninety percent of the muscle memory already in place.

Measurable outputs

Each example reports its own cycle time against SLA.

Every example reports its own cycle time against the configured SLA. The dashboard carries a tile per process with the median, the ninetieth percentile, and the breach count for the trailing thirty days. Ops leaders tune the processes against the measurements rather than against anecdotes, which keeps the operating rhythm grounded in which flows are working and which need attention.

Rollout timing

Eight examples live inside the first ninety days.

Across teams that deploy Strkr BPA, the eight examples on this page typically land live inside the first ninety days. The discount approval and the onboarding chain usually ship in week two. The renewal motion and the legal routing in week four. The remaining four by day ninety. The pace is set by operations clarity, not by platform limits, which is the right fit for a tool built around revenue BPA rather than enterprise orchestration.

Eight business process automation examples, ninety days to live.

Discount approvals, Closed Won onboarding, ninety-day renewal, legal clause routing, QBR cadence, sales-to-CS handoff, executive escalation, partner co-sell. Every example lives in the same canvas with the same primitives, with the audit trail stitched to the deal timeline and the dashboard carrying the cycle-time measurements.

Start free trial See pricing

Common questions

What buyers ask about this feature.

Are these worked examples real deployments or marketing illustrations?

Both. The eight examples on this page are drawn from the deployments that show up most often in the first ninety days of real customer rollouts across revenue teams in SaaS, services, and B2B product organizations. The numbers (Marcus, Priya, sixty thousand dollar deal) are composite rather than from a single named customer, but the shape of each flow is the production shape teams run against today. Named references are available on request for buyers evaluating the fit.

How long does it take to build the discount approval example?

A sales ops lead who has used the Strkr canvas before builds the three-tier discount approval chain in two to three hours. The limiting factor is almost always policy clarity (the finance team naming the thresholds) rather than the tool. For teams that already have the policy documented, the build itself fits inside an afternoon. For teams that discover the policy during the build, the clarification conversations extend the timeline but produce a tighter policy at the end.

Can we customize these examples for our specific business?

Yes. The eight examples on this page are starting shapes that every team customizes for their own policy, their own stage names, their own segment definitions, and their own approver roles. The customization is a configuration task on the visual canvas rather than a code change. Teams usually ship the first customized version in the first week and iterate against the production data in the following weeks as they observe which decisions reveal policy ambiguity.

How does the audit trail work across all eight examples?

Every example records a timestamped event for each step: the trigger, each condition evaluation, each approval decision, each delegation event, each document generation, each notification, and the final state transition. The log is a first-class report queryable in the standard report builder with saved views that auditors sign off on in advance. Clause versions pin to the decision date so historical records reference the policy in force at the time, not the current one.

Does Strkr integrate with DocuSign or Adobe Sign for the contract signing step?

Yes. The e-sign dispatch block supports DocuSign, Adobe Sign, Dropbox Sign, and any provider that exposes a webhook callback for completion events. The signed artifact returns to the deal automatically with the audit trail stitched to the deal timeline. For teams that need native e-sign without a third-party provider, Strkr Documents includes an in-platform signing experience, but the integration path keeps every major provider available for teams with existing contracts.

Is this HIPAA compliant for healthcare revenue teams?

Yes. Strkr is HIPAA compliant with a BAA available on request. PHI fields are tagged at the schema level and only merge into templates when the template is marked for PHI handling. The audit evidence captures the PHI flow so a HIPAA reviewer can trace which processes handled protected data. SOC 2 Type II certification is in progress through 2026-Q4. GDPR and CCPA compliance are already in place.

Related features

Pair this with...

Business Process Automation Business Process Automation Examples Business Process Automation Trends Business Process Automation Platforms Business Workflow Automation Workflow Automation

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing