Ninety-four pre-built flows the ops lead starts from.
The pre-built library covers the recurring patterns: inbound lead routing, pipeline hygiene, renewal flagging, invoice sends, customer onboarding, SLA escalation. The marketplace adds partner-contributed recipes for vertical motions. Starting from a working shape beats a blank canvas every time.
Ninety-four solutions sorted into eight categories.
The pre-built library ships with 94 verified flow templates across eight categories. Each template is a complete working flow configured against a sample tenant and tested in the sandbox. Teams import a template, swap fields, and publish. Most imports take under 20 minutes end to end.
Lead routing
Twelve inbound and outbound shapes.
Twelve routing templates: round-robin with territory, round-robin with capacity, weighted by rep performance, SDR-pool first then AE escalation, segment-based (SMB vs mid-market vs enterprise), timezone-aware for global teams, inbound demo rush, outbound SDR enrichment, partner-referred routing, event-booth lead capture, newsletter double-opt-in, cold-restart on dormant leads.
Nine billing templates: invoice-send-on-close, invoice-reminder-day-7, overdue-invoice-day-30, overdue-invoice-day-60, dunning-cadence with escalation, discount-approval routing, usage-tier-crossed alert, true-up invoice generation, and renewal-pricing refresh. Each integrates with Stripe or the configured payments provider.
Marketing
Eleven nurture and campaign templates.
Eleven marketing templates: MQL-to-SDR handoff, nurture-sequence enrollment by segment, cold-restart on dormant contacts, webinar follow-up, content-download attribution, UTM-tracked campaign roll-up, re-engagement after 90 days silent, lifecycle-stage automation, score-threshold alert to sales, double-opt-in enforcement, and unsubscribe propagation across channels.
Projects and delivery
Ten project motions.
Ten project templates: new-deal-to-onboarding-project auto-create, sprint-end roll-up, blocker-flagged escalation, release-ready notification, retro reminder, capacity-at-risk alert, overdue-task reminder, external-stakeholder notification, scope-change approval, and project-complete handoff. Each writes against Strkr Projects or the integrated external PM tool.
External integrations
Fifteen webhook and connector recipes.
Fifteen integration templates: Slack post on new deal, Slack post on closed won, Slack daily digest, Teams post on at-risk account, Google Calendar sync for exec meetings, DocuSign auto-send on contract-stage, Jira ticket creation on bug-report, Zendesk ticket on NPS detractor, Stripe webhook consumer, HubSpot bidirectional sync, Salesforce field sync, Google Workspace user provisioning, Microsoft 365 user provisioning, Okta role sync, and SIEM audit forward.
Compliance and audit
Six governance templates.
Six compliance templates: GDPR data-subject-request handling, CCPA opt-out propagation, HIPAA PHI access logging, SOX quarterly review generation, change-control approval chain, and audit-export to the warehouse on a cron. These templates ship with the field mappings regulated industries need as a starting point.
How a template becomes your flow
Six configuration steps per import.
A template import is not a one-click installer. The ops lead walks six configuration steps, each surfacing the decisions the template needs mapped to the tenant. The six steps take 15-25 minutes for typical imports and prevent the common failure where a template fires with wrong-tenant assumptions.
Step one
Pick the template.
The library view shows templates sorted by category with a search and a filter. Each template card displays: name, one-line purpose, typical setup time, prerequisites (integrations required), and the number of tenants currently using it. The ops lead reads the card and clicks import on the one that fits.
Step two
Map the trigger.
The import flow prompts for the trigger: which object, which event, which filters. The template suggests defaults (lead-created with source=inbound), the ops lead confirms or adjusts. The trigger map is explicit; nothing fires until the step completes.
Step three
Map the fields.
Fields the template reads and writes get mapped to the tenant's actual field names. Classic case: template references lead.industry, but the tenant uses lead.industry_segment. The mapper surfaces the fields side by side and the ops lead confirms the pairing. Missing fields prompt a create-field step if the admin role allows.
Step four
Pick the users.
Templates that reference users (owner assignment, approver on an escalation chain, notification recipient) prompt the ops lead to pick specific users or roles. The pattern "notify the Sales Manager" gets wired to the actual user holding the role, not left as a template placeholder.
Step five
Sandbox against sample records.
Before publish, the sandbox runs the imported flow against a sample record and shows the trigger evaluation, every condition, every action. The ops lead confirms the shape works. Destructive actions display what would have been written. Classic catch: a template designed for a two-stage pipeline runs against a tenant with a four-stage pipeline, and the sandbox surfaces the mismatch before anything fires.
Step six
Publish and tag.
Publish promotes the imported flow to live, prompts for an owner, a review cadence, and a priority. The imported flow lands in the management library with full lifecycle tracking from the first live run. No orphan imports; everything is governed from the moment it fires.
The marketplace
Partner-contributed recipes for vertical motions.
The pre-built library handles the horizontal patterns. The marketplace adds vertical and partner-contributed recipes: a healthcare-intake flow from a Strkr implementation partner, a construction-RFP flow from a vertical SI, a legal-matter-intake flow from a legal-tech ISV. Each marketplace entry is verified by Strkr RevOps before publication.
Verified partner recipes
Reviewed by Strkr RevOps.
Marketplace entries from partners go through a verification pass: Strkr RevOps imports the recipe against a sample tenant, runs it through the sandbox, confirms the field mappings and the stated purpose match. Verified recipes carry a visible checkmark. Unverified community-contributed recipes exist but display a visible unverified flag.
Vertical starters
Healthcare, legal, construction, SaaS.
Vertical starter packs bundle recipes specific to a vertical: healthcare patient-intake plus HIPAA access logging plus referral tracking plus insurance verification; legal matter-intake plus conflict check plus retainer invoice plus retention trigger; construction RFP intake plus bid tracking plus submittal workflow plus closeout. Each pack is one import that produces 6-12 configured flows.
Ratings and reviews
Honest feedback from live users.
Each marketplace entry shows rating (1-5 stars), install count, and reviews from live users. Reviews are moderated for accuracy but not for favorability; a one-star review with a complaint stays visible. Partners see the feedback and iterate; ops leads shopping for a recipe read before they install.
Attribution
Credit to the author.
Marketplace recipes carry an attribution to the author (partner firm or community contributor). The author stays visible in the audit log for the imported flow, which is useful when the ops lead has questions six months later and wants to reach the original author. Attribution is a first-class field, not an afterthought.
Updates
Partners can push revisions.
Partners who publish a recipe can push a revision when the underlying motion changes. Tenants running the recipe receive an update notification with a visible diff and an opt-in action. Nothing updates silently; tenants decide whether to adopt the new version. Partners get the ability to maintain recipes without replicating per-tenant installs.
Fork and privatize
Import once, make it yours.
An imported recipe can be forked into tenant-private state. The fork breaks the update link and makes the recipe fully owned by the tenant. Teams that want to customize deeply without receiving partner updates fork early. Teams that want to stay on the partner-maintained version stay unforked.
What this replaces
The DIY builder, the consultant, the dead template.
Without a solutions library, teams either build every flow from scratch, hire a consultant to configure the standard motions, or import a template that was tested six quarters ago against a different version of the platform. Each path has a failure. The library addresses them directly.
DIY blank canvas
From scratch is slow and error-prone.
Building a lead-routing flow from scratch takes 3-4 hours even for an experienced ops lead because the edge cases (OOO handling, capacity caps, SLA escalation) require trial and error. A template import handles the same scope in 20 minutes because the edge cases are pre-solved. The savings compound across 40 flows.
Consultant setup
Expensive and still needs maintenance.
The classic BPM playbook is a six-figure consulting engagement to configure the standard flows. Six months later, the business changes and the consultant is gone. Strkr's library plus the management surface means mid-market teams configure the standard motions themselves and own the maintenance. No consulting line.
Stale template libraries
HubSpot and Salesforce libraries drift.
The HubSpot and Salesforce template libraries exist but have drifted over the years as the underlying products shift. Half the templates reference deprecated fields. Strkr RevOps maintains the library actively; drifted templates get flagged and either refreshed or retired. The library is a live product, not a Q2-2022 artifact.
Not Zapier zap gallery
Middleware templates do not fit the record.
Zapier's zap gallery is a middleware-centric view: trigger in system A, action in system B. The templates are useful for cross-system glue but not for in-record motions. Strkr's library runs inside the record, so a routing template actually assigns the lead on the lead record instead of writing an attachment field through a Zapier intermediary.
Not Make.com scenarios
Same middleware story at a different price point.
Make.com scenarios are templates for the Make workflow builder. Same critique: middleware-centric, not record-centric. Strkr's solutions library targets the operational flows that live inside the system of record. Teams running both occasionally find the right split; we never recommend a middleware tier for jobs that can live natively.
Open API ecosystem
Vertical ISVs build and sell their own.
A vertical ISV (healthcare EHR integration partner, legal practice management partner, construction software partner) builds a recipe pack for their customer base and distributes via the Strkr marketplace. The ISV monetizes the recipe pack separately from the Strkr subscription. The ecosystem produces vertical depth without Strkr building every vertical in-house.
The ninety-day deployment plan
Five waves that cover the common motions.
Teams that import from the solutions library typically run a five-wave plan across ninety days. Each wave covers a motion area and lands 6-10 live flows. By day 90 the team runs 30-50 flows against the library and the handful of custom motions specific to their business. The sequencing matters more than the content.
Wave one
Lead routing and hygiene (week 1-2).
Start with the inbound routing templates and the Monday hygiene sweep. These are the two highest-ROI motions and the easiest to measure. Expect 8-12 flows live by end of week two. The wins are visible immediately and the executive sponsor sees the first results in the first standup.
Wave two
Customer success (week 3-4).
Add the health-score and renewal templates. These share records with the sales motions, so the integration points are already warm from wave one. The CSM team sees adoption lift because the templates surface risk signals they were manually hunting before.
Wave three
Billing and marketing (week 5-7).
Billing templates integrate Stripe (or the configured payments provider) with the pipeline. Marketing templates wire the nurture sequences. These are more technically involved and benefit from the earlier flow experience. The expansion catches the ops lead at the right skill level.
Wave four
Projects and integrations (week 8-10).
Add the project motions (new-deal-to-onboarding-project, release notifications) and the external integrations (Slack posts, Teams alerts, Google Workspace provisioning). The integration layer is the bridge to the rest of the stack; by this wave the ops lead can wire the connections confidently.
Wave five
Compliance and vertical (week 11-13).
Finish with the compliance templates (GDPR, CCPA, HIPAA access logging) and any vertical starter packs. The compliance layer closes the loop with the risk and legal teams. The vertical packs produce the differentiated motions that the horizontal library did not cover.
Walk the solutions library and import three flows live.
Bring your top three pain points. We will find the matching recipes, map the fields, and ship them against your sandbox on screen.
Are the templates free, or is there a marketplace fee?
The pre-built library of 94 verified templates maintained by Strkr RevOps is free and included on every paid tier. The marketplace, which hosts partner-contributed and community recipes, includes both free entries and paid entries. Paid marketplace entries carry a one-time or subscription fee set by the author; the Strkr platform takes a modest cut and the author receives the rest. Verified partner starter packs for specific verticals typically fall in the paid tier because they bundle 6-12 recipes with pre-wired integrations.
Can we contribute our own flows back to the library or marketplace?
Yes. Any tenant can submit a flow as a marketplace recipe. The submission flow prompts for a name, purpose, prerequisites, and a usage note. Strkr RevOps reviews submissions for safety (no leaking tenant-specific data, no hardcoded credentials, no destructive patterns) before publication. Approved recipes publish under the submitting user's attribution. The pattern is useful for consulting partners and vertical ISVs who want to productize their expertise and reach the Strkr customer base.
What happens when a Strkr platform update changes a template requirement?
Strkr RevOps maintains the pre-built library actively. When a platform change affects a template, RevOps updates the template and pushes a revision; tenants running the template receive an update notification with the change and an opt-in action. Nothing updates silently. The management surface tracks the version of each imported template, so the audit trail shows exactly which version of a template a tenant is running at any point. This matters for retroactive debugging and for compliance audits.
Can we fork a template, modify it, and keep receiving updates?
No. Forking a template severs the update link because the forked version has diverged from the upstream. Tenants that want to receive updates stay on the unforked version and configure through the standard field mappings and user picks. Tenants that need deeper customization fork early and own the maintenance from that point. The admin surface warns before fork so the choice is explicit; the fork is reversible only by re-importing the template fresh.
How do verticals like healthcare or legal get served without Strkr building every vertical?
Vertical depth comes from the partner marketplace. Vertical ISVs and consulting partners build recipe packs for their domain (healthcare EHR integration, legal matter intake, construction RFP tracking) and distribute through the marketplace. The ISVs know the vertical better than Strkr does, so the content is more accurate than if Strkr tried to build every vertical in-house. The platform provides the engine; the ecosystem provides the vertical motions.
Is HIPAA covered for the healthcare templates in the marketplace?
Yes for tenants signed on the BAA. The templates themselves do not touch PHI during installation; they install configuration metadata that then runs against the tenant's own records. When the templates execute against live PHI, the standard tenant encryption, audit logging, and access controls apply. SOC 2 Type II attestation is in progress for 2026-Q4. Marketplace partners contributing healthcare recipes must sign the Strkr partner agreement which includes PHI-handling clauses before their recipes can be verified for HIPAA scenarios.
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.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
