Customertimes × Cursor · Product Vision

Rosetta

We speak your org's language.

The AI-native delivery stack for enterprise business-critical platforms — from org discovery through deploy, without writing custom code.

DiscoveryDeliveryAdoption
The shift

Code is becoming a commodity. Context and adoption are the value.

  • Agents can now configure enterprise platforms — not just write code.
  • The bottleneck moves to context: machine-readable platform & tribal knowledge.
  • And to adoption: trust, governance, and change management.

Rosetta supplies both — it turns business intent into platform configuration an agent can execute, and lands through a credible 4-hour discovery.

The blind spot

Today, AI tooling is sold to developers only

# developers × devices × consumption

That ceiling misses the largest technical population in every enterprise — the people who run business-critical platforms but are not counted as "developers."

The new market

The enterprise-platform Center of Excellence

  • CoEs are run by business consultants, product owners, BAs, and declarative consultants — not Java engineers.
  • No one builds an in-house "SAP custom dev team." These platforms are configured, not coded.

"I don't need my developers to be 20% more efficient. I need a completely different point of view — a SaaS replacement, or reducing the CoE of my business-critical apps."— Enterprise CEO, on what he actually wants

What it is

One platform, two layers

Layer 1 — Discovery

Reads the org, produces reports

Read-only OAuth → ingest metadata & event logs → 12 executive-grade reports in 4–6 hours. One scan arms the CFO, Head of Sales, CIO, and VP of Platforms.

"What a Big-4 partner charges $250K to produce — generated in hours."

Layer 2 — Delivery

Changes the org, carries decisions forward

Turns requirements into configuration, not just code — flows, automations, validations — via CLI with full diff review.

Scope decisions carry forward into the build through a versioned crosswalk.

The lifecycle

One platform for the whole implementation lifecycle

  • Intake — workshops, documents, Excel, ServiceNow, existing Salesforce orgs.
  • Requirements — generate business & product requirements from raw inputs.
  • Estimate & plan — effort estimates and sprint plans, ready to execute.
  • Configure → Docs & QA — partial config automation, documentation, and test artifacts.
  • Knowledge — every project enriches the repository, smarter next time.
Positioning
20–50%

AI is the engine. Consultants orchestrate.

  • The goal isn't full automation — it's AI reliably doing 20–50% of the implementation.
  • Humans validate architecture, business decisions, and complex configuration.
  • Not "AI replacing consultants" — consultants become product operators who improve the knowledge that powers the next project.
Why "Rosetta"

It translates three languages that don't talk to each other

Businessrequirements · decisions · tribal knowledge
PlatformSalesforce · SAP · ServiceNow config
AgentCursor + an LLM that can act

Like the Rosetta Stone, the product is the translation layer between intent, platform, and execution.

The moat

We package enterprise knowledge for agents

  • By default, declarative docs for SAP, Databricks & much of Salesforce are invisible to agents — so a raw run hits trial-and-error and endless loops.
  • Rosetta packages proprietary + tribal knowledge into agent-consumable form (instruction files → RAG that returns instant answers).
  • Cutting the loop improves output and increases Cursor consumption — a structural win for the partnership.

Think context7 — but proprietary: Customertimes' accumulated knowledge of how to configure these platforms correctly.

Beyond software

Institutional knowledge becomes the asset

A private, Context7-style repository of docs, patterns, config examples, snippets, and tribal knowledge — enriched by every project, monetizable on its own.

Implementation templates Testing templates BPMN generation Config playbooks Process-mining templates Industry patterns
Three motions

One platform, three ways to win

Salesforce

Implementation accelerator

Analyze environments, find optimizations, speed deployments, support migrations — Veeva → Life Sciences Cloud.

Direct

AI-powered SI

Differentiate Customertimes as a platform, not consulting capacity.

Cursor & Anthropic

Reusable assets

Frameworks, accelerators, configuration knowledge, templates, MCP integrations that drive adoption.

How we engage

Land on a 4-hour scan. Expand two ways.

Play 1 — Exoskeleton

Evolution, not revolution

Drop into an existing CoE and speed it up without ripping anything out. Turn an 80-person Salesforce CoE into power-user builders. Lowest-risk land.

Play 2 — SaaS replacement

A different point of view

Rebuild expensive platform workflows with Cursor-powered, identical-behavior config — e.g. a Marketing Cloud replacement. Higher value, handled with care.

Motion: Discovery → Scope → SOW → Config → UAT → Training, then recur via delta scans & managed change.

Why it works

A win on both sides of the partnership

For Cursor

A new TAM beyond developers

Unlocks the enterprise-platform CoE — business users who never showed up in "how many developers do you have?" — plus more consumption per seat.

For Customertimes

From billable hours to transformation

Shifts the revenue base to discovery, configuration, migration, adoption & the knowledge layer — without cannibalizing managed services.

The expansion

One pattern, every business-critical platform

NowSalesforce family13+ clouds · Agentforce
NextTableau · MuleSoftin flight
ThenServiceNow · Dynamicssame playbook
PrizeSAP · Workday · Databricksthe CoE at scale

Every platform with a Center of Excellence is the same opportunity: translate intent into configuration an agent can run.

The thesis

Configuration is commoditizing. Context and adoption are the new value. Rosetta owns the translation between them — and turns a services business into an AI-native transformation business.

Next steps

Shape the play with Cursor

  1. 1 Define the product vision (1–2 page doc) & compile all use cases.
  2. 2 Build an end-to-end POC: intake → analysis → estimation → sprint → config → docs → QA.
  3. 3 Formalize the Cursor partner motion (intro → Elise Martisic).
  4. 4 Align on the roadmap early next week.

rosetta@customertimes.com · Built on Cursor — MCP-native, BYO LLM, diff-reviewed.

01 / 12
/ Space next · back · F fullscreen