The tenant has reported a repair. You’re waiting for the landlord’s go-ahead, the contractor needs access, and the tenant is asking what’s happening. The latest answer is somewhere in an email thread.
What belongs to one job
Property and reported issue
Landlord approval
Contractor and access arrangements
Latest update and next action
Follow one repair from the first report to confirmed completion.
Here’s how the proposed workflow could fit together. These are process illustrations, not finished software or real client records.
Bring the repair history together
Match the tenant’s report, photos and messages to the property. Create or update the repair record in the tools we agree, and flag missing access details.
Repair record created
Tenant’s report
Leaking tap
Property reference
Matched
Photos and messages
Linked to repair
One repair record in your system
Coordinate the work order
Record the landlord’s approval and agreed appointment against the repair. Pass missing quotes or access arrangements to the right person, with messages approved by your team.
Work order coordinated
Landlord approval
Recorded
Contractor appointment
Added
Access details
Confirmed
Agreed details stay with the job
Check the completed repair record
Save the contractor’s completion evidence and update the property system through the assessed connection. Verify the saved status; your manager checks the work before the job is closed.
Completion record checked
Contractor evidence
Saved
Property system
Updated
Saved status
Verified
Your manager checks before closing
Urgent issues stay with your team and existing emergency process. The pilot does not authorise expenditure, appoint contractors or decide legal repair deadlines.
From the first call to a workflow your team can use
1
Walk through the work together
Show us an anonymised example of a recurring job and the tools your team uses. On the audit call, we choose one workflow with a clear start and finish.
2
We connect the steps in your tools
We build the agreed workflow around your WhatsApp, email, Slack and business systems: bringing in information, checking it and updating the right records. We agree scope, price and access in writing first.
3
Test the work from start to finish
We run through cases with your team and check the result in the destination system. Unclear cases go to a person. Your team approves every outgoing message before it is sent.
Help shape Runnrr as a founding client
Runnrr is new. We’re looking for firms willing to test one real workflow with us and tell us what works and what needs to change.
80% off
Pay 20% of the normal price for the agreed pilot scope. Your written quote shows both prices, what is included and any third-party costs. We agree the scope and timing with you.
I’ve been helping companies move their work forward with digital products for more than ten years. After Corgee, I worked with Eneba and Easygenerator on new products and process automation. At Easygenerator, that included helping companies such as PepsiCo and Danone.
Now I help small and medium-sized businesses automate work in the tools they already use. We start with a small scope, written data terms and results your team can check. The companies above are part of my previous experience, not Runnrr customer references.
Privacy and practical questions
Can the AI processing run on our own hardware?
We can scope local AI inference for the agreed workflow. We assess the model and hardware, then test the setup before using live data. Connected services such as WhatsApp, email and your business systems keep their own processing and storage arrangements; we document those separately. This is a custom setup assessed for your firm, not a standard feature included with every pilot.
Where will our data live?
That depends on the tools and workflow we agree. Before connecting live data, we document the systems, hosting locations, providers, retention and deletion arrangements in your pilot’s data terms. We do not promise that all processing stays on your device or in one country.
Who can see our data?
We agree the named people and service providers who need access before setup. Access is limited to the agreed workflow. Start the conversation with an anonymised example; do not send client records through the enquiry form.
Which steps stay with our team?
We agree which system changes need approval and how incomplete work or exceptions return to your team. Your team reviews and approves every outgoing message. Those controls are defined before we connect live data.
What does the 80% discount apply to?
The founding-client pilot costs 20% of the normal price for the same agreed scope. Your written quote shows both prices, what is included and any third-party costs. There is no published fixed fee or standard duration; further work needs a separate agreement.
Is this already a finished industry product?
No. Runnrr is new. These are workflows we propose to configure and test with founding clients, not a catalogue of ready-made industry integrations. We assess the workflow and your tools before agreeing what to build.