Todo -> Requirements
The client request becomes required workflow steps, evidence, legal constraints, owners, and acceptance criteria.
Software agency owners and delivery leads
Software House Workflow Mapping
Bring the workflow you rejected as too complex. We map todo, requirements, capabilities, risk, and Auto / Assist / Manual execution in 7 days.
Simple mental model
Todo -> Requirements -> Capabilities -> Risk -> Auto / Assist / Manual
A workflow is not a static checklist. Robo maps what has to happen, which requirements constrain it, which capabilities are available, what the Risk Map allows, and whether each step runs automatically, with assistance, or manually.
Capabilities -> Risk
Drone availability, IoT sensor availability, package capabilities, documents, and legal constraints feed the Risk Map before execution mode is selected.
Auto / Assist / Manual
Execution can switch step by step: automated where capability and risk allow it, assisted when review is needed, manual when fallback is safest.
30-second mental model: Hybrid Energy Audit Process
Previously, Collect Energy Data carried required_manual: true as a fallback. Now the Risk Map decides. If Drone available is true, the outdoor inspection switches from manual work to Automated Aerial Inspection. If IoT sensors available is true, energy readings move from manual collection to Retrieve Sensor Data. The software house does not build three separate apps; it maps requirements, capabilities, and risk-controlled execution modes.
Collect Energy Datarequired_manual: true fallbackRisk Map decisionDrone available -> Automated Aerial InspectionIoT sensors available -> Retrieve Sensor Data
Real showcase library
Three real showcases from the repository, not a generic starter kit.
Bring the workflow you rejected as too complex; we map it in 7 days using real process packs, commands, drivers, risk assessment, investment analysis, and monitoring setup.
Energy audit
prepare_energetic_audit.json, insepction_outdoor_energetic_audit.json, recomendation_eneretic_audit.json, implement_fix_energy.json with risk_assessment, investment_analysis, and monitoring_setup.
Data Center
command/data_center contains AdjustTemperatureCommand.cpp, CheckPowerUsageCommand.cpp, DiagnoseServerCommand.cpp, OpenRackCommand.cpp; process/data_center/server_check.json shows the server-check workflow.
Big Companies
build_office.json, buy_ground_for_office.json, factory_relocation_plan_v2.json, and relocation_excecution_planning.json model office building and factory relocation execution.
Proof
Store, GitHub, and trial path make it obvious this is infrastructure for your stack.
Store
See why you will not copy this in 2 weeks: legal-pl-energy-audit -> legal-office-pl -> legal-office-core + energy-audit. Every package has an npm-like dependency graph.
legal-pl-energy-audit -> legal-office-pl -> legal-office-core + energy-audit
Open Store
GitHub
This is not no-code. These are SDKs you plug into your stack: pip install robo-connector-sdk; composer require robo-meister/robo-store-api robo-meister/flow-beacon-api robo-meister/context-engine-api.
pip install robo-connector-sdk
composer require robo-meister/robo-store-api
composer require robo-meister/flow-beacon-api
composer require robo-meister/context-engine-apiTrial
Sandbox workspace with $5 credits, about 50k calls, and a ready-made organisation containing the Energy, Data Center, and Big Companies showcases. See a todo switch from manual to auto when you add capability.
Request trial accessBefore / after
Before
You receive a request for an audit system with legal standards, reports, investments, and monitoring. You build a camera app for 30k, a new EED standard appears, the client calls because they fail inspection, and the project dies.
After
You take packs from the Store, compose a workflow that works whether the client has a drone or not, the Risk Module decides whether the step runs automatically or with assistance, Robo Store updates legal-office-core, and dependent packs get the update. You take 50% forever as a Pack Partner.
7-day pilot shape
From client pain to a demoable integration path in one week.
Day 1
Pick the painful workflow
Choose one client workflow and define owner, trigger, documents, approval, and success metric.
Deliverable: Signed pilot boundary and success metric.
Day 2
Map systems and events
List source systems, event names, fields, webhook expectations, and security boundaries.
Deliverable: Event map with source system and fields.
Day 3
Connect sandbox API
Create a test token, call the workflow endpoint, and send the first event from a script or client mock.
Deliverable: Authenticated sandbox call and first event trace.
Day 4
Configure workflow proof
Create the visible workflow, owner handoffs, document/evidence state, and exception queue.
Deliverable: Demo workflow with owners and exception queue.
Day 5
Validate webhook and retries
Register callback handling, idempotency expectations, test failures, and trace IDs.
Deliverable: Webhook/retry checklist and trace IDs.
Day 6
Show client demo
Demonstrate before/after, audit evidence, human approvals, and where the existing system stays in place.
Deliverable: Client-ready before/after demo.
Day 7
Choose commercial path
Decide whether this is referral, joint implementation, custom delivery, or reusable package work.
Deliverable: Commercial path and pack/no-pack decision.
Jesteś dev? Pierwszy call w 5 minut
Start from the same /developers quickstart, then package distribution can move into a .rappkg with meta.json, workflows/, and drivers/.
export TOKEN="paste-test-token-here"
curl -s https://robo-meister.com/api/v1/workflows.json -H "Authorization: Bearer $TOKEN"Commercial paths
Choose the commercial path after the 7-day pilot.
Model
What you do in 7 days
How you earn
Referral
Introduce client and business pain
Lead share, referral fee
Joint Pilot
Discovery, local context, rollout support
Project margin
Pack Partner
Own repeatable niche know-how
50% of pack subscription, forever for Early Pack Partners, tracked usage
API Partner
Build connector, portal, or app layer
Client services + platform usage model
Resources
Resources
Download the partner PDFs after the 7-day pilot and pack path are clear.
PDF
Open PDF
Partner Quick Overview
Short introduction for first partner conversations.
PDF
Open PDF
Partner Business Guide
Detailed guide explaining partner models, cooperation paths, pilot flow, and objections.
PDF
Open PDF
Solution Catalog
Catalog of solutions, packages, modules, and first workflow examples for client conversations.
PDF
Open PDF
Software House Offer Brief
One-page offer for software houses: starter kit, first integration ideas, 7-day pilot shape, and commercial paths.
Ready to map the first workflow?
Bring one current workflow, the owner, where it stalls, and the outcome you want to improve.