Longshift.Concept brief · The Orchestrator · Oct 2026 · Internal draft
Concept brief

The blank page
that already knows.

Longshift opens to an empty chat. Underneath it, an orchestrator agent has already read your business and the domain skills you've loaded. It speaks first only when a skill says the moment is right. The rest of the time it stays quiet.

The idea

Quiet by default. Ready when it counts.

Most software waits for you to ask. Most assistants interrupt too often. The Orchestrator does neither. It sits beneath the canvas and is primed by domain skills: packaged knowledge of how a type of business runs, what to watch for, and when to act. It does its homework before you type, so the first thing you see is already shaped by the work that matters today.

01 · READ

Understands the domain

Reads the business domain, the connected systems and the loaded skills before the first keystroke.

02 · WEIGH

Waits for the right moment

Each skill defines when acting is worth it. If no trigger is met, the agent says nothing.

03 · OFFER

Starts the useful thing

It opens a thread, prepares a draft, flags an anomaly or suggests the next step, and always leaves the decision to you.

Mockup 1 · Before you type

An empty canvas, already arranged.

The chat is blank. The hidden agent has picked the two things worth your attention this morning and placed them as quiet cards. Nothing blinks, and nothing asks for attention it hasn't earned.

Longshift.MONDAY · 07:52 Good morning, Jan. Two things are worth a look before 10:00. Everything else can wait. ORDER-TO-CASH3 orders blocked on credit limitCHF 48,200 waiting · oldest 2 daysReview → DRAFT READYReminder to Hofmann AGInvoice 30 days overdue, polite toneOpen draft → Prepared by the Orchestrator · 2 of 41 signals passed the bar Ask anything, or just start…
Shaped, not crowded. 41 signals were read and only 2 were shown.
Mockup 2 · It speaks first

A thread you didn't have to start.

A skill trigger fires: the trend in customer payment behaviour has changed. The Orchestrator opens one thread, explains why in a sentence, brings the evidence and offers a next step. One tap continues it; dismissing it teaches the bar.

Longshift. Orchestratorstarted this thread · via skill wholesale-o2c Kessler Bau has started paying 18 days later than usual. Three invoices in a row have slipped, and their open balance is now 74% of their credit limit. I'd suggest a short check-in before the next delivery ships on Thursday. DAYS TO PAY · LAST 8 INVOICES +18d Draft check-in email Hold shipment Not now Why now: matches trigger “payment drift ≥ 14 days with an open order”. Confidence high · first alert this month. Reply to the Orchestrator…
It always says why. Every proactive thread names the skill, the trigger and its confidence.
Mockup 3 · Skills shape the room

Load a skill. The workspace learns the trade.

Domain skills are the Orchestrator's expertise. They come from Longshift's skill builder (longshift-skills), which turns research on a market segment into a pack: a domain skill, a -help skill, and simulator skills for apps and data. Enabling a pack quietly changes what the agent watches for, how it talks, and what lands on the canvas.

Longshift. SKILLS wholesale-o2cOrder-to-cash for wholesalersLoading wholesale-o2c-helpAnswers in the trade’s own wordsReady wholesale-o2c-sim-dataSafe sample data to rehearse onReady WHAT CHANGES WatchesCredit limits, payment drift, open backorders SpeaksDunning, delivery notes, price lists ProposesReminders, credit reviews, reorder drafts Stays silent onRoutine postings and anything below threshold Wholesale skills active · 4 new triggers armed Ask about orders, credit, delivery…
Same calm shell, a different expert. The pack names follow the longshift-skills pack convention, using its wholesale order-to-cash method example; the triggers shown are illustrative.
The bar

Earn every interruption.

A proactive agent is only valuable if silence is its default. That's why the bar for initiating is deliberately high.

1Only a skill trigger can start a thread; the agent never speaks just because it's idle.
2It needs evidence from your own systems, and it shows that evidence.
3There's a time-sensitive action you can take now, not just an observation.
4There's a daily budget of a few proactive threads; anything beyond waits in a quiet digest.
5Every “Not now” raises the bar for that trigger.
6It drafts and suggests, but never sends, books or changes anything without your approval.

Not another dashboard. Not another chatbot.
A colleague who has already read the file and knows when to stay quiet.

Possible second wave
Not in scope for v1

Projections and layers by domain

Once the Orchestrator understands a domain, the same skills could project it spatially: a map of deliveries and routes for logistics, or rooms per site, project or customer for trades and construction. These would be optional layers over the same calm canvas, listed here as a possible second wave and not as a commitment.

Positioning

The Orchestrator in one line

Longshift reads your business before you do, and speaks only when it matters.

For SMEs who'd rather run the business than run the software: the domain expertise comes from skills, the initiative comes from the Orchestrator, and every decision stays with you.