03 / Marketing ops
Supergentic
Fieldhaus
The problem
The product names its own problem: the blank page. A journey, a segment or an email in Marketing Cloud each start from nothing.
Marketers know what they want in words. Supergentic starts from those words and hands back something ready to refine, export or build on.
How it was built
I designed it around one move, learned once: describe the goal, press Generate, refine the draft. The rest of the product is that move applied to every kind of Salesforce work.
- 01
One sentence, a whole journey
Type what you want and the Journey Wizard returns an eleven-step welcome journey with a yes and no split, the blocks it will create and a refine box. The page opens on one sentence box, not an empty canvas.
One sentence in, a branching journey out. The reply is scripted. - 02
A builder that writes the sentence
For people who do not know what to type, a five-step Prompt Builder writes the sentence for them. Each choice adds a fragment, so the prompt grows as you click.
The Prompt Builder writes the sentence as you click. - 03
Results with next moves
A result arrives with a refine box and chips, the list of blocks it will create, and Save as Blocks. A journey can also leave as an Agentforce prompt template.
A generated welcome series with a refine box and the blocks it will create. - 04
One pattern everywhere
Flows, segments, content and campaigns open the same way: a prompt box, suggestion chips, one Generate button, the caption "Powered by AI · You can refine after generation", and saved work below. Learn it once.
A flow from a sentence, on the same prompt pattern. - 05
A segment you can read twice
A segment arrives as criteria beside its audience breakdown, with the SQL it stands for one click away.
A segment with its criteria, audience and SQL. - 06
Three drafts per channel
Content Studio writes three variants per channel, each with a rendered preview, in the brand voice you set.
Three variants per channel, with a rendered preview. Sample brand. - 07
Superpowers
A gallery of 140 named automations across the clouds. A six-phase wizard builds a new one: capabilities, tools, goal, planning, review and naming.
Building a superpower in six phases. - 08
One noun for everything
Every artifact is a block: 40 block types and 103 seed blocks, shown as cards in a grid, a list or a map, with type, status and cloud filters and a drawer for details, preview and export.
Building Blocks as a grid, a list and a map. - 09
A Console that shows its work
Each Console reply starts with a monospace tool-call line, then prose, then data cards, then follow-up buttons. Six one-character shortcuts open pickers: @ for integrations, $ for data sources, # for blocks, ! for powers, * for sample data and / for frameworks.
A Console reply: a tool-call line, then data cards and follow-ups. Scripted. - 10
More clouds behind one switch
The sidebar runs Superpowers, App Lab and Building Blocks, then a group per cloud. Unfinished groups carry a Beta or Alpha tag and appear only when their flag is on, so one switch brings five more clouds into view.
One Labs switch turns on more clouds in the sidebar. - 11
Leaving the app
Exports are real files: JSON, CSV, XML and YAML in the shared export dialog, and eight file types across the app, from SQL to HTML.
An export from a catalog list. Sample products. - 12
Dark first, a colour per cloud
The interface is dark first, with an orange accent and a blue brand colour, and each cloud gets one colour for its chips, card edges and Generate buttons. A light theme, density and font size come from Settings.
The same journey in the light theme. - 13
Keys for people in a hurry
Cmd+K opens a command palette and L jumps to Labs. In demo mode, V types a sample prompt into an empty field and C clears it.
The command palette on Cmd+K. - 14
App Lab
The newest part turns sources into a project with a live preview. It is wired to a real model and says plainly when no model key is set.
App Lab: sources on the left, reference templates on the right.
The solution
A clickable product across 43 screens: the landing page and 42 app routes, from Superpowers and Building Blocks to the Journey Wizard, Console, Data Hub, Sales Tools and App Lab.
Downloads, clipboard copies, search, filters, block editing, saved work, themes and Labs flags all work. Generation and Console replies are scripted from local data; App Lab calls Claude through a server-side proxy when a model key is set.
Decisions along the way
Script the AI first
Replies stream from local data, so every screen could be judged before a model was involved. The proxy to a real model was scaffolded only in the last week.
Both platforms from week one
Support for the older Marketing Cloud Engagement and the newer Marketing Cloud Next went in together on the fourth day, so no block is tied to one of them.
Tiers for what is unfinished
Newer features sit behind Labs flags in beta and alpha tiers. The console was moved down to alpha and off by default until it earned its place.
Fewer views, working buttons
Board and map views of the block library were removed, the list view was fixed, and the drawer buttons were made to do what they say.
What I delivered
- A Superpowers gallery of 140 automations and a six-phase wizard
- Building Blocks: 103 seed blocks in grid, list and map views
- Journey, Flow, Segment, Content and Campaign builders on one prompt pattern
- A Console with tool-call lines, data cards and shortcut menus
- Data Hub and Customer 360 on sample data
- Sales Tools that turn a request into SOQL and Salesforce metadata
- Exports in eight file types
- App Lab, a project generator wired to Claude through a server-side proxy
Value added
For marketers
Work starts from a sentence or a guided builder instead of an empty canvas, and leaves as files the next tool can read.
For the design
One prompt pattern, reused on every builder, means the product is learned once.
By the numbers
Commits per week, spring 2026
86 commits between 30 March and 17 May, in three bursts.
View as table
| Period | Value |
|---|---|
| 30 Mar | 22 |
| 6 Apr | 16 |
| 13 Apr | 32 |
| 20 Apr | 0 |
| 27 Apr | 2 |
| 4 May | 0 |
| 11 May | 14 |
Source: git history of the Supergentic repo
The result
Supergentic is a working demo. Its screens, builders, blocks and exports run on local sample data, and generation and Console replies are scripted. App Lab is wired to live Claude calls through a server-side proxy and stops with a plain notice when no model key is set.
Results
- 43routed screens
- 140superpowers in the gallery
- 86commits, 30 March to 17 May 2026
What I took from it
The blank page was the real problem, so the design answer was one sentence box everywhere. Giving every result its next moves, a refine box, the blocks it creates and an export, is what turns a demo into a workspace.
Background
Salesforce sells two generations of the product Supergentic targets. Marketing Cloud Engagement is the established platform. Marketing Cloud Next was announced on 11 June 2025 as an agentic marketing platform built on the core Salesforce platform. A tool that starts from plain language has to produce work for both, which is why Supergentic supported both from its first week.