The mission lifecycle
What happens between a goal and a result
Eight steps. You decide at every one.
- 1
You describe the goal
Plain language, the way you would say it out loud. A deadline, a budget, a target number or a restriction are optional extras.
- 2
Parallel asks what it needs
Only the questions whose answer would change the plan. Each one is a choice, a slider or a date, and says why it matters.
- 3
It diagnoses before it plans
Parallel says what it understood and what limits the goal, names the routes, picks one, and says why it drops the rest.
- 4
One recommended plan
One route, not three. Stages on real dates, measurable steps, the risks and assumptions, and what it needs from you.
- 5
Your agent team is built
One button builds the team from the plan. Each agent gets a role, its tools, a schedule, a success metric and a permission level.
- 6
You set the boundary
Say what agents may do alone, what needs approval, and what they may never do.
- 7
The mission runs
Agents work the schedule and produce the deliverables. Anything consequential waits in Approvals, with the action, the reason, the risks and the exact preview.
- 8
It measures, adapts and reports
Planned against actual, every day. When it falls behind, Parallel names the assumption that broke and tells you what it changed.
What Parallel will and will not claim
A planner that overstates its confidence is worse than no planner.
It will say
- "Recommended": the best expected return under your constraints.
- "Expected 4 to 7 replies": an estimate from measured data, not a promise.
- "Assumption: you can respond within a few hours."
- "Confidence: medium. Based on 27 messages."
- "Simulated": anything the demo did not really perform.
It will not say
- "87% chance of success": a made-up number dressed as analysis.
- "Guaranteed three clients."
- That an email was sent when it was only drafted.
- That it researched something it could not reach.
- That a plan is working when the numbers say otherwise.
It measures the result, not the activity.
Every mission tracks the number you asked for. When it falls behind, Parallel changes the steps that depend on the assumption that broke.
Example mission · simulated figures
New clients
On plan
PlannedActual
- Day 3Replies at 4%. The plan expected 10%.
- Day 3Assumption that broke: a discount is enough to get a reply.
- Day 4Changed: the first message now opens with a free website check.
- Day 12Replies at 11%. Seven new clients so far.
Agents prepare. You decide.
Emails, posts and payments wait as drafts until you approve them. Research and writing run on their own.
Send 14 emails to clinics in Logroño
- To
- 14 clinics from your list
- Subject
- I checked your website's booking form
Nothing is sent until you approve.
Security, in short
- Keys and access tokens are encrypted and never shown again after you save them.
- Each agent uses only the apps and actions you gave it.
- Every agent action is logged. You can pause a mission at any moment.
- Your data is never sold or used for advertising.
Questions
What happens if a step fails?
It stops, tells you what happened, and offers to retry, change the step or hand it to you.
Do I have to connect my apps first?
No. You connect an app when a step needs it, not before.