Match the current filters
Try the work.
See the logic.
Explore the thinking behind a SaaS dashboard and an enquiry automation. Change the data. Follow the decisions. See what happens next.
Fictional samples. Real interactions.
01 / A SMALL SAAS WORKSPACEA clearer view
A clearer view
of the moving parts.
Filter projects, update a status, or complete a task. Every number and chart is calculated from the sample data currently in view.
Demo data only. These invented projects, estimates and dates are not client results, revenue or performance claims.
Fictional project estimates
13 of 20 visible tasks
Across the current results
Older activitySample period ends 26 Oct 2026
| Project | Estimate / updated | Status |
|---|---|---|
| ₹62,0003 days ago | ||
| ₹48,0006 days ago | ||
| ₹85,00012 days ago | ||
| ₹36,00019 days ago | ||
| ₹72,00026 days ago |
5 fictional projects shown. Select a project to explore its tasks.
02 / FOLLOW THE FLOWAn enquiry comes in.
An enquiry comes in.
A useful record comes out.
Step through an n8n style workflow with Python style processing. Inspect the input, validation, scoring and duplicate handling as they happen.
This runs entirely in your browser. No n8n workflow, Python runtime or external API is executed. No CRM is connected and no message is sent.
INPUT / FICTIONAL ENQUIRY
Use fictional details only. Editing the payload starts a fresh run. The included addresses use the reserved .example domain.
See the Python style scoring rules
email = enquiry["email"].strip().lower()
name = " ".join(enquiry["name"].split())
score = 40
score += 30 if budget >= 50000 else (
15 if budget >= 25000 else 5
)
score += 20 if service == "automation" else 10
score += 10 if len(message) >= 30 else 0
priority = "high" if score >= 75 else "standard"Illustrative Python. Equivalent JavaScript runs the calculation in this browser. These rules are sample business choices, not a prediction of lead quality.
PROCESS / INSPECT EACH STEP
- 01Sample enquiryNext step
- 02ValidateWaiting
- 03Normalise & scoreWaiting
- 04Sample CRMWaiting
- 05Notification previewWaiting
Workflow output
Browser simulation{
"status": "waiting_for_sample_input",
"external_requests": 0
}1 sample CRM record in this run. Reset restores one seeded contact. Notification output is a preview only.
Simulation ready. No external services are connected.
The interface is one part.
The decisions make it useful.
A production build adds your actual data model, access rules, integrations, validation and monitoring. This lab is a small, inspectable example of how I approach the pieces.
Talk through your idea