01
WORKWAY
Build workflows with TypeScript.
Deploy to the edge.
Monetize in the marketplace.
02
The Problem
Existing tools move data from A → B. That's not a workflow.
A workflow is a compound outcome:
- Meeting ends → Notion page created
- → Slack summary posted
- → Email draft generated
- → CRM updated
Four services. One outcome. No one does this well.
03
"When the tool is truly ready-to-hand, it withdraws from our attention. We don't think about the hammer—we think about the nail."— Martin Heidegger, Being and Time
04
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ ZUHANDENHEIT │ │ (Ready-to-hand) │ │ │ │ The ideal state: │ │ ───────────────────────────────────────────────────────────────── │ │ │ │ You think about → "meetings that follow up on themselves" │ │ → "CRMs that update themselves" │ │ → "emails that write themselves" │ │ │ │ Not about → OAuth tokens │ │ → API pagination │ │ → Error handling │ │ → Rate limits │ │ │ │ The tool should disappear. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Tools recede. Outcomes remain.
05
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ VORHANDENHEIT │ │ (Present-at-hand) │ │ │ │ When tools break into visibility: │ │ ───────────────────────────────────────────────────────────────── │ │ │ │ ✗ "Error: OAuth token expired" │ │ ✗ "Rate limit exceeded. Retry after 3600s" │ │ ✗ "Field 'user_id' is required" │ │ ✗ "Connection timeout after 30000ms" │ │ │ │ This is where DX fails. │ │ The tool becomes visible when it should be invisible. │ │ │ │ WORKWAY's job: push Vorhandenheit to the edge. │ │ Handle it once, so developers never see it. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
The SDK absorbs complexity so workflows remain clear.
06
Intent-Based SDK
You write what you mean, not what you need to do.
ai.synthesize()— notAIModels.LLAMA_3.generate()integrations.gmail.send()— notOAuth.refresh().then(fetch(...))trigger: webhook()— notaddEventListener('POST', ...)
Minimal surface area. Predictable patterns. The SDK recedes.
07
A Workflow
export default defineWorkflow({
name: 'Meeting Follow-Up',
integrations: ['zoom', 'notion', 'slack', 'gmail'],
trigger: webhook({ service: 'zoom', event: 'meeting.ended' }),
async execute({ trigger, integrations, ai }) {
// Get the transcript
const transcript = await integrations.zoom.getTranscript(trigger.meetingId);
// Synthesize (not "call AI model")
const summary = await ai.synthesize(transcript, {
format: 'action-items'
});
// Distribute
await Promise.all([
integrations.notion.createPage({ title: trigger.topic, content: summary }),
integrations.slack.send({ channel: '#meetings', text: summary }),
integrations.gmail.draft({ to: trigger.participants, body: summary })
]);
return { success: true };
}
});Intent-based. Four services. One outcome. The tool disappears.
08
Taste as Moat
The marketplace is not an accumulation.
It is a curation.
"Weniger, aber besser" — fewer workflows, but better ones.
Quality surfaces. Noise prunes itself.
09
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ QUALITY SIGNALS → DEVELOPER SUPPORT │ │ The platform catches problems before users do │ │ │ │ ┌─────────────────┬───────────────────────────────────────────────┐ │ │ │ Reliability │ Success rate, error recovery, uptime │ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Engagement │ Active installs, 30-day retention, re-purchase│ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Code Quality │ Zuhandenheit score, error handling, docs │ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Community │ Ratings, reviews, forks │ │ │ └─────────────────┴───────────────────────────────────────────────┘ │ │ │ │ <70% success (30d) → Alert + support ticket: "Needs attention" │ │ <50% success (7d) → Moved to "Needs Work" (still accessible) │ │ Zero installs (3w) → "Dormant" status (one-click reactivation) │ │ │ │ Developers get support. Users get quality. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
10
Developer
Keep 100% of subscription fees you charge.
Set your own price. Own your customer relationship.
Platform
5¢ per light execution.
25¢ per heavy execution.
First 20 runs free per workflow.
11
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ ARCHITECTURE │ │ Honest about what's open and what's proprietary │ │ │ │ ┌───────────────────────────────────────────────────────────────┐ │ │ │ PLATFORM (Proprietary - SaaS) │ │ │ │ Workflow Engine • Marketplace • Billing • Analytics │ │ │ └───────────────────────────────────────────────────────────────┘ │ │ ↑ │ │ API calls │ │ ↑ │ │ ┌───────────────────────────────────────────────────────────────┐ │ │ │ SDK (Open Source - Apache 2.0) │ │ │ │ @workwayco/sdk • @workwayco/integrations │ │ │ └───────────────────────────────────────────────────────────────┘ │ │ ↑ │ │ imports │ │ ↑ │ │ ┌───────────────────────────────────────────────────────────────┐ │ │ │ CLI (Open Source - Apache 2.0) │ │ │ │ workway init • test • build • publish │ │ │ └───────────────────────────────────────────────────────────────┘ │ │ │ │ Developers can build locally without infrastructure. │ │ Platform handles execution and payments. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
12
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ THE HERMENEUTIC CIRCLE │ │ │ │ .ltd (Philosophy) │ │ │ │ │ provides criteria for │ │ ↓ │ │ WORKWAY (Research) │ │ │ │ │ validates │ │ ↓ │ │ Workflows (Practice) │ │ │ │ │ applies to │ │ ↓ │ │ Clients (Services) │ │ │ │ │ tests and evolves │ │ ↓ │ │ .ltd (Philosophy) │ │ │ │ Each workflow published tests the philosophical foundations. │ │ Marketplace feedback evolves the canon. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
The circle closes when practice informs philosophy.
13
Agentic by Design
WORKWAY is optimized for AI code generation.
- Minimal surface area — fewer methods to hallucinate
- Predictable patterns — consistency prevents errors
- Self-documenting types — Claude reads JSDoc
- Rich error messages — guide self-correction
The goal: Claude writes workflows so naturally the SDK becomes invisible.
14
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ CLAUDE CODE INTEGRATION │ │ The development environment as a force multiplier │ │ │ │ ┌─────────────────┬───────────────────────────────────────────────┐ │ │ │ CLAUDE.md │ Ethos, patterns, philosophy baked into context│ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Skills │ "workway-debug", "workflow-review" on demand │ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ MCP Servers │ Direct Cloudflare access (KV, D1, R2, Workers)│ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Slash Commands │ /deploy, /audit-canon, /test-workflow │ │ │ ├─────────────────┼───────────────────────────────────────────────┤ │ │ │ Hooks │ Pre-commit validation, type checking │ │ │ └─────────────────┴───────────────────────────────────────────────┘ │ │ │ │ Claude doesn't just write code. It understands the philosophy. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
The Subtractive Triad applied to development itself.
15
┌─────────────────────────────────────────────────────────────────────────┐ │ │ │ SMALL TEAM SUPERPOWERS │ │ Built by 1 engineer. Maintainable by 2-3. │ │ │ │ Claude Code + Cloudflare + TypeScript = │ │ │ │ ┌─────────────────────────────────────────────────────────────────┐ │ │ │ • Full marketplace with quality curation │ │ │ │ • Multi-tenant workflow execution (Durable Objects) │ │ │ │ • Global edge deployment (<50ms cold starts) │ │ │ │ • Built-in billing & revenue share (Stripe Connect) │ │ │ │ • OAuth for 12+ integrations │ │ │ │ • AI inference at the edge (Workers AI) │ │ │ └─────────────────────────────────────────────────────────────────┘ │ │ │ │ Traditional stack: 8-12 engineers, 18 months │ │ This stack: 1 engineer, 1 year → launch Dec 5. 1-3 can scale it. │ │ │ │ The constraint enables the outcome. │ │ │ └─────────────────────────────────────────────────────────────────────────┘
Weniger, aber besser — applied to team size.
16
Get Started
# Install the CLI
npm install -g @workwayco/cli
# Create your first workflow
workway init my-workflow
# Test locally (no cloud dependencies)
workway test
# Publish to marketplace
workway publishLocal-first. Test without external deps. Deploy without ops.
← → navigate f fullscreen