These journeys describe how you go from curious visitor to someone with a running AutoBlock. For developer machine setup, see the repo root README.md — this guide stays on the product path.
Journey A — Curious visitor (5 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Read the home page | autoblocks.pro |
| 2 | Compare Starter vs Plus | autoblocks.pro/pricing |
| 3 | Ask the help chat a question | Help button (bottom of marketing pages) |
| 4 | Skim a doc article | autoblocks.pro/docs |
Outcome: You understand what AutoBlocks does and whether Phase 1 fits your needs.
flowchart LR
Home["Home"]
Pricing["Pricing"]
Help["Help chat"]
Docs["Docs"]
Decision{"Ready to try?"}
Home --> Pricing --> Decision
Home --> Help --> Docs --> Decision
Decision -->|Yes| Signup["Journey B"]
Decision -->|Not yet| Docs
Journey B — Start free trial (10 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Click Start trial | autoblocks.run/signup |
| 2 | Create account | Signup form |
| 3 | Complete onboarding | /onboarding |
| 4 | Activate first AutoBlock | Onboarding final step |
| 5 | View your dashboard | /routines |
Outcome: One enabled AutoBlock tied to your workspace.
| Onboarding choice | Recommended if… |
|---|---|
| Beginner + template | You want the fastest path |
| Technical + template | You plan to use webhooks soon |
| AI path | You can describe your goal in a sentence |
Detail: Templates and onboarding.
Journey C — Template power user (15 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Browse templates | /templates |
| 2 | Open Webhook forwarder | /templates/webhook-forwarder |
| 3 | Create AutoBlock | → /routines/new?template=webhook-forwarder |
| 4 | Copy inbound webhook URL | Routine detail |
| 5 | Send test POST | curl or your tool |
| 6 | Confirm in Activity | /activity |
Outcome: Event-driven automation with verified webhook trigger.
Journey D — Scheduled daily habit (10 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Pick Morning summary template | /templates/morning-summary |
| 2 | Set schedule time + timezone | Wizard (desktop for cron) |
| 3 | Customize notification message | Wizard step |
| 4 | Enable AutoBlock | Activate |
| 5 | Wait for first tick | Check /activity |
Outcome: Recurring notification without manual runs.
Requires worker service in production (autoblocks-worker on Render).
Journey E — Upgrade after trial (5 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Review usage meters | /billing |
| 2 | Compare limits | autoblocks.pro/pricing |
| 3 | Choose Starter or Plus | /billing checkout |
| 4 | Complete Stripe Checkout | Stripe hosted page |
| 5 | Return to app | /billing — plan active |
Detail: Billing and plans.
Journey F — Fix a failed run (5 minutes)
| Step | Action | URL |
|---|---|---|
| 1 | Open Activity | /activity |
| 2 | Find failed run | Red status badge |
| 3 | Read plain-language error | Run detail |
| 4 | Open AutoBlock | /routines/[id] |
| 5 | Fix config or use AI repair | Wizard / AI panel |
| 6 | Re-run manually | Run button (manual trigger) |
Detail: Troubleshooting.
Journey map (all paths)
flowchart TB
Visitor["Visitor on .pro"]
Trial["Signup + onboarding"]
Active["Active user"]
subgraph paths [Common paths]
T["Templates"]
AI["AI assist"]
WH["Webhooks"]
SCH["Schedules"]
end
Visitor --> Trial --> Active
Active --> T
Active --> AI
Active --> WH
Active --> SCH
Active --> Billing["Billing / upgrade"]
Quick reference — first week
| Day | Suggested action |
|---|---|
| 1 | Complete onboarding with one template |
| 2 | Run manually once; check Activity |
| 3 | Adjust notification or schedule |
| 4 | Browse second template |
| 5 | Enable email-on-failure in Settings |
| 6 | Review trial usage on Billing |
| 7 | Decide Starter vs Plus before trial ends |
Where to get help
| Need | Resource |
|---|---|
| Product questions (logged out) | Help chat on autoblocks.pro |
| How-to articles | autoblocks.pro/docs |
| Account issues (logged in) | Activity + Settings |
| Full manual | This docs/user/ series |