KENYA · GUIDE 0596 · EDITION 4.2
No-code workflow building in Kenya
Build a small no-code workflow around an approved business task.
A CONCRETE EXAMPLE · ILLUSTRATIVE
Fictional no-code flow FLOW-96 uses AppSheet to turn a furniture repair enquiry into an internal review task. Fields are RequestID, SubmittedAt, Category, Owner and Status. New approved requests start'Review needed'; a bot creates one internal task and records completion state. Output is an owner-controlled prototype, five fixtures and pause/recovery instructions. Customer messaging, payments and unapproved external data connections are excluded.
Who is the first customer?
Owner-managed firms with repetitive administration.
Test the offer
Demonstrate the workflow with fictional records and failure cases.
What your operating pack contains
- A business-specific operating guide PDF
- Offline itemised costing and quotation tool
- Supplier request and sales message drafts
- Job-card and quality-response documents
- Offline operations desk: supplier comparison, work checkpoints, accepted deliveries and cash tracking
- Cashflow and launch review: downside scenarios, break-even, 13-week cash plan and trial decision
- Source register and unresolved checks
Delivery and quality
Workflow performs only approved actions and failures remain visible.
Cost drivers
- integrations
- runs
- exception handling
Use your own supplier quotations. Worked figures in the pack are illustrative and do not establish a verified startup budget or profit forecast.
Evidence and scope
Bots: The Essentials — AppSheet ↗
Events/processes and testing; free-account test email restrictions and external-source triggers matter. · Checked 2026-10-26
Rights Of A Data Subject ↗
Kenyan privacy principles and data minimisation; not a complete compliance assessment. · Checked 2026-10-26
Import data from data sources (Power Query) ↗
Import preview and data-source workflow; version-specific menus may differ. · Checked 2026-10-26