11/09/2026
One of the most common things we hear at the start of an engagement.
"We want to automate our maintenance process."
Great. Which part? Who triggers it? Where does the data live? Who approves what? What happens when the contractor doesn't reply?
Most people haven't thought past the first sentence. That's not a criticism. It's just that nobody ever told them what an automation partner actually needs to start building.
So here it is.
Five things. Write these down before any conversation and you'll save yourself three weeks of back and forth.
The trigger. What starts this process? An email arriving? A form being submitted? A date being reached? A button being clicked? Be specific. "Someone requests maintenance" is not a trigger. "A tenant submits the repairs form on the website" is.
The steps. What happens next, in order? Write it out like you're explaining it to someone who's never done your job. Every step. Including the ones that feel obvious.
The data. Where does the information come from? Which system holds the tenant record? Where do contractor details live? Is it one spreadsheet or four? This is the question most people haven't answered before they come to us.
The decision rules. Where does a human make a judgement call? Who approves repairs above a certain cost? What gets escalated and what doesn't? If it lives in someone's head, write it down. If you can't write it down, it can't be automated.
The output. What does done look like? A notification sent? A record updated? A document generated? A payment queued?
That's it. One page. Those five things.
It won't be perfect. It'll raise questions you hadn't thought of. That's the point. The brief isn't the finished spec, it's the starting point that makes the first conversation actually useful.
Save this. Send it to whoever handles your operations. Fill it in before the next time someone says "we should automate that."
COMMENT the word BUILD. I'll send you the one-page brief template we give every client before we start. No strings. Just useful.