RENDR
Can I model complexity?
Home renovation without the WhatsApp chaos.
The workflow engine below is real and interactive. The renovation framing is illustrative.
Build an approval flow (add steps, set single or multi-reviewer rules), then run the sample application through it and see how the decision moves, stalls, or gets rejected. This is the same engine RENDR would run: swap "Legal" and "Brand" for "Architect" and "Structural," and the model is identical.
Build the flow
No steps yet. Add an approval step to build your workflow.
Run an application
Activity log
Why each transition happenedIllustrative personal experiment: intended benefits are marked as such, not as measured results.
-
The problem
A renovation project runs through a chain of people who all have different responsibilities, approvals, documents, and dependencies: homeowner, architect or designer, contractor, subcontractors, suppliers, inspector. Right now that chain runs on WhatsApp threads, and a single discovery (say, a contractor finding unexpected plumbing behind a planned kitchen wall) turns into 27 messages instead of one clean decision: issue raised, contractor adds photos and a proposed change, architect reviews, homeowner sees the cost and time impact, homeowner approves, contractor proceeds, work is verified, change is closed.
-
What the prototype models
The tool above is a generic multi-party approval engine: stages, reviewers, and a rule per stage (any one reviewer, or all of them). That is deliberate. The same shape that resolves "kitchen tiles require your approval" also resolves "brand review before this campaign ships." Multi-party approval is one abstraction with many faces.
RENDR itself would not show this builder to a homeowner. It becomes the shared operating layer between everyone on a renovation, not one generic project-management view, but a different interface per person based on what they actually need to do. A homeowner never sees a workflow engine; they see "Kitchen tiles require your approval, +JOD 320, no schedule impact. Approve / Ask a question."
-
Other flows the first real version would model
Quote → review → approve. Material selection → client approval → procurement. Change request → cost impact → approval. Milestone → inspection → payment release. Defect → assign → fix → verify. Contractor handover → homeowner acceptance.
Connected thinking
- How we can work together Workflow design, permissions, states, and exceptions are the core of most of my enterprise engagements.