Worked Examples
Real, end-to-end Nembl setups for common SMB processes. Each example walks through the Service, Offering, Form, Workflow, Inbox, and Responsibilities as one cohesive build — not just isolated reference. Use these as starting templates: clone the structure, change the names, adapt to your team.
Each example assumes you've finished Getting Started so you've already created a Company and submitted at least one test request.
Pick an example
| Example | Process modeled | Best for | Setup time |
|---|---|---|---|
| IT Support — New Laptop | Hardware request → manager approval → IT fulfillment → notify requester | Internal IT teams | 20 min |
| Employee Onboarding | New hire → parallel tracks for HR paperwork, IT setup, manager intro | HR + Operations | 30 min |
| Vendor Approval | New vendor request → procurement review → finance approval → DocuSign | Finance / Procurement | 25 min |
| Customer Refund | Refund request → CSM review → finance approval → Stripe action | B2B SaaS / Customer Success | 25 min |
| Marketing Brief Intake | Brief request → triage → assign to designer → review → publish | Marketing teams | 20 min |
How to use these examples
- Read the example end-to-end first. Don't start clicking until you understand the shape — knowing where you're going makes the build go fast.
- Adapt the names to your context. "IT Support" → "DevOps Helpdesk". "Manager Approval" → "Tech Lead Sign-off". The structure transfers; the labels are yours.
- Build incrementally. Get the basic Service + Offering working first (~5 min), then add the Workflow, then Responsibilities, then Agents. Don't try to ship everything at once.
- Test as a different user. Once built, sign in as a teammate (or use a separate browser profile) and submit a request as a regular user. You'll catch UX issues your admin view doesn't show.
What if my process isn't here?
Most processes are variations of these five shapes:
- Single-decision — submit, one approver decides yes/no, done. (Vendor Approval)
- Multi-stage approval — submit, multiple sign-offs in sequence. (Customer Refund)
- Parallel fulfillment — submit, multiple teams work simultaneously. (Employee Onboarding)
- Triage-then-route — submit, intake decides which queue handles it. (IT Support)
- Creative back-and-forth — submit, draft, review, iterate. (Marketing Brief)
Pick the closest example and adapt. If you're stuck modeling something genuinely new, see the FAQ for a process-design checklist.