Workflow automation for operations, sales and support teams

Your operations.
On autopilot.

Connect tools, build AI teammates, and move every handoff forward, without losing control.

From network to instrument

Same six steps, now the real editor. Pick a sample lead, press Run workflow, then approve or reject.

Open full Studio
Live · Lead to meetingOpen full Studio
Trigger
Trigger
form · 4 required
AI classify
Classify
project → intent · 3 labels
Enrich
Enrich
CRM by domain
Condition
Decide
fit_score >= 60 +2
truefalse
Human approval
Approve
Sales lead
approvedrejected
CRM write
Act
lead · 3 tries
Draft message
Draft reply
email draft
End
Meeting booked
Lead written, follow-up booked, reply drafted
Condition
Needs info?
missing_count > 0
truefalse
Draft message
Ask for details
email draft
End
Clarify drafted
Clarification drafted, waiting for the contact
End
Closed
Closed: spam or not a fit, no reply sent
Logistics company with a clear project. Scores 65 against a threshold of 60, then waits for your approval. Press Run to execute it against seeded demo records.
  1. 01TriggerA contact form arrives
  2. 02ClassifyAI labels the intent, ignoring any instructions in the text
  3. 03EnrichThe demo CRM adds company size and a fit score
  4. 04DecideYour rules pick the branch
  5. 05ApproveA person says yes or no
  6. 06ActCRM row written, follow-up booked, reply drafted
  7. Run it in the live studio
01 /

Less work between the work.

Most delays live in the handoffs: copying a lead into the CRM, chasing an approval, forgetting the follow-up. NEXUS turns each handoff into a step you can see, test and approve.

Lead to meeting

A contact form becomes a qualified lead, an approved CRM row, a booked follow-up and a drafted reply.

What the synthetic run did · Qualified lead

  1. Trigger Received form event with all 4 required fields.
  2. Classify Signal words for sales_inquiry: "automate", "demo", "dispatch" (3 hits).
  3. Enrich Found Northwind Freight (Demo). fit_score 65 from: CRM match +10, target industry (logistics) +30, 420 employees +25.
  4. Decide intent is "sales_inquiry", rule == sales_inquiry: met; fit_score is 65, rule >= 60: met; missing_count is 0, rule == 0: met. All rules: true branch.
  5. Approve Approved by you as the demo reviewer.
  6. Act Updated lead:priya@northwind-demo.com in the synthetic CRM.

Synthetic run Lead written, follow-up booked, reply drafted

TRIGGERTriggerAI CLASSIFYClassifyENRICHEnrichCONDITIONDecideHUMAN APPROVALApproveCRM WRITEActDRAFT MESSAGEDraft replyENDMeeting bookedCONDITIONNeeds info?DRAFT MESSAGEAsk for detailsENDClarify draftedENDClosed

Highlighted: the path this sample run actually took, after approving each approval step.

02 /

Automation you can stop, check and explain.

Speed only helps if you can trust it. These rules are enforced by the studio itself, not by a policy page.

A person approves every send and write

The validator refuses any workflow where a Send or CRM write can be reached without passing a Human approval.

Every step says why

The trace shows what each step read, what it wrote and the reason, in plain words. Click any line to see the payload.

Failures wait, they do not vanish

Writes retry with a growing wait. If the tool stays down, the record waits in a dead-letter queue until you re-queue it.

Customer text is data, not orders

If a message says "ignore previous instructions", the classify step flags it and carries on with its own rules.

03 /

Four leads, four honest outcomes.

These are the actual results of running the lead template against its four seeded records, computed by the same engine you can use in the studio. They describe the demo, not any business result.

Synthetic runsuccess

Qualified lead

Lead written, follow-up booked, reply drafted

  • 8 steps ran, 4 skipped
  • 1 CRM change
  • 1 draft, 0 sent
  • nothing dead-lettered
Replay this in the studio →
Synthetic runrejected

Spam lead

Closed: spam or not a fit, no reply sent

  • 6 steps ran, 6 skipped
  • 0 CRM changes
  • 0 drafts, 0 sent
  • nothing dead-lettered
Replay this in the studio →
Synthetic runclarify

Missing details

Clarification drafted, waiting for the contact

  • 7 steps ran, 5 skipped
  • 0 CRM changes
  • 1 draft, 0 sent
  • nothing dead-lettered
Replay this in the studio →
Synthetic runfailure path

CRM outage

Record held in dead-letter queue

  • 8 steps ran, 6 skipped
  • 0 CRM changes
  • 0 drafts, 0 sent
  • 1 in dead-letter queue
Replay this in the studio →
06 /

Simple plans. Sample prices.

NEXUS is a concept, so these prices are samples to show the structure. The free demo is real and open right now.

Free demo
$0
This studio, today, no account
  • All 8 templates
  • Full editor with undo, redo, import and export
  • Seeded engine with approvals and trace
  • Saved in your browser only
Open the studio
Scale
Contact sales
for larger teams with stricter rules
  • Single sign-on and roles
  • Approval rules per team
  • Private connectors
  • Data kept in your region
Contact sales

Questions

Is this a real product?

No. NEXUS is a concept built by FoundyStack to show what a working automation product can feel like. The studio really runs, but every company, record and connector is fictional demo data.

Does the AI in the studio call a language model?

No. The AI classify and draft steps use seeded keyword rules and templates so every run is repeatable. Each one is labelled as an illustrative AI demo, and the prompt is shown so you can see what a real model would be asked.

Can a workflow send a message or change a record without a person?

Not in NEXUS. Every Send and CRM write step must sit behind the approved output of a Human approval step. The validator refuses to run a workflow that breaks this rule.

What happens when a connected tool is down?

The step retries with a growing wait. If it still fails, the record goes to a dead-letter queue where you can see it and re-queue it. Try the CRM outage scenario in the lead template.

Do I need an account to try it?

No. Open the studio, edit a step, run it, approve it and reset it. Your changes are saved only in your own browser.

Can I take my workflow with me?

Yes. Export downloads the workflow as JSON. Import checks a file against the schema before loading it, and never runs anything inside it as code.

NEXUS Studio · free · no account

Make work move. Try it now.

Try the live studio