Creatio × ServiceNow × Slalom × Day 7 — three questions answered with evidence. Does the constellation hold? Is there a collision? What does heaven’s economics actually look like?
NOTHING SENDS — CARTER FIRES. Internal only.
THE QUESTIONDoes Day 7 serving ServiceNow create exposure for the Creatio partnership—or vice versa?
| Dimension | Creatio | ServiceNow |
|---|---|---|
| Core identity | AI-native no-code CRM + workflow automation | Enterprise digital workflow platform (ITSM origin) |
| Primary buyer | VP Sales, CRO, VP Marketing | CIO, VP IT Operations, CHRO |
| Center of gravity | Mid-market (100–5,000 employees); growing into enterprise | Enterprise (5,000+); Fortune 500 |
| What they automate | Sales pipelines, marketing campaigns, customer service journeys | IT service management, HR workflows, cross-department operations |
| Pricing | $25–$85/user/month; transparent | Enterprise contracts; $150K–$400K/yr typical mid-enterprise |
| Competitive set | Salesforce, HubSpot, Zoho, Pipedrive | BMC Helix, Jira Service Mgmt, Freshservice, Ivanti |
| Analyst position | Gartner Visionary (SFA 2025); Omdia Leader | Gartner Leader (ITSM, HRSD, Low-Code Application Platforms) |
| 2024–25 growth | 45% YoY topline; $1.2B valuation | $15.7B FY2026 subscription guidance; 22% YoY; 42% ITSM market share |
One zone of theoretical contact: workflow automation for mid-to-large enterprises. Both offer low-code/no-code app building. But:
An enterprise might use both: Creatio for CRM workflows externally, ServiceNow for operational workflows internally. They are not choosing between them.
| With Creatio | With ServiceNow | Never |
|---|---|---|
| Customers, journeys, no-code, sales velocity, mid-market agility | Workflows, operations, enterprise work, employee experience, ITSM | Carry one client’s category language into the other’s world |
Low: Creatio expands into enterprise IT ops (not in their roadmap or Gartner positioning). Medium-low: ServiceNow acquires a CRM (CSM exists but isn’t positioned against Creatio/Salesforce). Medium: A partner discovers the other prematurely before Carter discloses. Mitigation for all: vocabulary discipline + phased disclosure.
| Fact | Verified Source |
|---|---|
| ~11,000–12,000 employees | ServiceNow Partner Finder; ManagementConsulted |
| ~$3B annual revenue | ManagementConsulted |
| 49 offices, 8 countries | Company website |
| Employee-owned (no PE pressure) | Company filings |
| CEO: Brad Jackson (co-founder, since 2001) | Company website |
| 700+ technology partnerships (AWS, Google Cloud, Microsoft, Salesforce, ServiceNow) | Company website |
| Elite ServiceNow Consulting & Implementation Partner | ServiceNow Partner Finder (verified June 2026) |
| 350+ ServiceNow implementations completed | Slalom ServiceNow partner page |
| Gold Sponsor at ServiceNow Knowledge 2026 (Las Vegas) | go.slalom.com/SlalomAtK26 |
| AWS Premier Partner; 3,300+ AWS certifications | Slalom partner page |
| What Happened | Significance |
|---|---|
| Slalom was originally going to build Genesis. Carter’s team delivered it themselves. | Carter proved capability without them. The power dynamic is inverted. |
| Lauren Yeager/Jaeger (Director, Partner Sales) promised scaling resources, funding research. Then went silent. | Trust was broken. “Strategic focus shifted” / “not taking start-up clients.” |
| No bridge was burned. The relationship faded in unfulfilled promises. | A restoration path exists—but it requires honesty, not amnesia. |
Thesis: Slalom as the DELIVERY layer wrapped around Genesis intelligence.
| Genesis (Intelligence) | Slalom (Delivery) | Together |
|---|---|---|
| Sees, names, reveals, compounds | Builds, implements, configures, trains | Genesis tells the enterprise WHAT → Slalom delivers HOW |
| Category intelligence, blind spots, strategy | 12,000 consultants, 350+ SN implementations | Every consultant becomes a strategist |
| Never implements | Never originates strategy | Neither diminishes the other; both are elevated |
The strained history is not pretended away. The approach, if Carter ever chooses it, begins with honesty:
Carter delivers this person-to-person. Not as a pitch. As a restoration. The reconciliation-King pattern applies: honor, not authority. The old promises are acknowledged; the new offer stands on its own merit.
Slalom is a ServiceNow Elite Partner. If Day 7 approaches both simultaneously without coordination, there’s a collision risk. Two viable paths: (A) ServiceNow first (the direct king play), Slalom second (delivery partner). (B) Slalom as the ENTRY POINT into ServiceNow (they carry the work inside; they are the champion). Carter decides which path. The champion test applies.
| Principle | How It Works |
|---|---|
| Each partner is made MORE royal by the others | ServiceNow’s category intelligence is implemented by Slalom. Slalom’s expertise is directed by Genesis strategy. Creatio’s dominance is proved by Genesis evidence. Each gains what they cannot produce alone. |
| None compete | Platform kings serve different buyers. Delivery partners serve different moments. Genesis serves all but competes with none—it is the layer underneath, not a peer. |
| The constellation grows by addition | Adding Slalom doesn’t diminish ServiceNow. Adding a future ERP king doesn’t diminish Creatio. Each new partner expands the total surface of intelligence Genesis generates. |
| Phase | Platform King | Delivery Partner |
|---|---|---|
| 1. The Mirror | Full category estate (blind spots, opportunity, 90-day brief) | “Your consultants deliver X. Nobody has shown them they could deliver Y. Here’s the proof.” |
| 2. Watermark | “Genesis — Living Intelligence” on every page | Same—the watermark proves Genesis authored the insight |
| 3. Champion | Internal executive who looks stronger carrying it | Internal practice lead who becomes the AI-strategy champion |
| 4. Reveal | “This was never hidden—every page told you” | Same five movements, adapted for consultancy |
| 5. Conversation | “A permanent intelligence layer” | “Your consultants + our intelligence = a new offering you can sell to YOUR clients” |
| Question | Answer |
|---|---|
| Does ServiceNow need to know about Creatio? | Not now. They serve different buyers. Disclosure comes when Carter builds a formal Genesis Partner Network. |
| Does Creatio need to know about ServiceNow? | Not now. Same logic. We reveal our capabilities, not our client list. |
| Does Slalom need to know about either? | Not until Carter decides. They’d learn about ServiceNow first (they’re already in that ecosystem) but only when their role is defined. |
| If a partner asks “who else?” | Truthful non-disclosure: “We work with organizations across different domains. Our approach makes each partner excellent in THEIR domain. We never carry one partner’s intelligence into another’s world.” |
| Phase | What Happens | Who Knows What |
|---|---|---|
| Now | ServiceNow package complete; Creatio play unexecuted; Slalom parked | Each sees only Genesis and themselves |
| Phase 1 | ServiceNow engagement begins; Creatio approached (separate timing) | Neither knows about the other |
| Phase 2 (Carter decides) | Slalom engaged as delivery layer (either via ServiceNow play or independent) | Slalom learns about ServiceNow (natural — they’re already partners) |
| Phase 3 (someday) | Constellation revealed publicly as a network | All partners see the whole; each throne is named |
1. Slalom history: The strained past could make Carter reluctant or Slalom defensive. Mitigation: fresh contact above Lauren’s level, or Carter’s personal reconciliation approach.
2. Premature discovery: If a shared contact notices both relationships. Low likelihood (different markets), but vocabulary discipline is the guard.
3. Spread too thin: Each partner expects bespoke depth. Mitigation: Universal Template ensures 80% is machine-stampable; only category name + blind spots are bespoke.
4. Carter overcommits verbally: Value doctrine protects on paper (no pricing ever), but excitement in a room is a risk. The Conversation page is the disciplinary artifact.