Examples
The first part of this page shows systems we built and use at REB Works. The pictures use sample data so nothing private is shown, but the systems are real. Further down are solutions we can build for your business.
One screen that shows what's happening, so you don't have to check five different apps.
Illustration with sample data
Built for REB Works
A map of every system the business relies on, which ones are connected, and which need attention. Server status updates live each time it's opened.
Illustration with sample data
Built for REB Works
Communications, money and work in one view, with live feeds from Outlook and Slack, so the day starts with what actually needs a decision.
Small, focused tools that do one job well, built around how your team already works.
YouFinance: summarise this week's invoices
REB Works appSent to the finance assistant. Only finance requests go there.
REB Works appSummary ready for your review.
Illustration with sample data
Built for REB Works
Type a request in Slack and it goes to the right assistant. Only approved people can send requests, and each request is checked against what that assistant is allowed to do.
Illustration with sample data
Built for REB Works
A searchable directory of every service the business uses, what it's for, whether it's been checked, and the evidence behind that status.
Repeating jobs that now run by themselves, with a person approving what matters.
Illustration with sample data
Built for REB Works
Email is sorted into folders, meeting requests become calendar entries, anything needing action becomes a task, and a short summary arrives twice a day.
Illustration with sample data
Built for REB Works
When a master document changes in SharePoint, the matching copy in a searchable notes library is updated. It currently runs in test mode while we check every file match.
Assistants with clear jobs and clear limits, so they help without surprises.
To: customer@example.com
Subject: Re: delivery date
Thanks for checking in. Your order is scheduled to arrive Thursday…
Waiting for your approval
Can send email only to the owner
Illustration with sample data
Built for REB Works
Drafts email, organizes the inbox and keeps the calendar tidy. It is technically blocked from emailing anyone except the owner, so every outside message waits for a person.
Each assistant works only in its own area
Illustration with sample data
Built for REB Works
A set of assistants, each with one role and read-only access to what that role needs. Requests outside a role's area are refused, and a person signs off on decisions.
Organized information that people and assistants can actually find.
| Supplier | Due | Category |
|---|---|---|
| Supplier A | Nov 14 | Software |
| Supplier B | Nov 20 | Office |
| Supplier C | Dec 1 | Hosting |
Illustration with sample data
Built for REB Works
Invoices stored in one SharePoint library, sorted into categories automatically, with due dates you can filter.
Illustration with sample data
Built for REB Works
A searchable store of decisions and context, so assistants answer from what was actually agreed, with a pointer to where it came from.
Illustration with sample data
Built for REB Works
The business's policies, guides and templates in one organized library, kept in sync and readable by the assistants that need it.
For your business
These are common jobs we set up for businesses, shown as examples. They use the same tools and approach as the systems above, adapted to how your team works.
Illustration with sample data
Example solution
When you hire someone, one form starts everything: accounts are requested, equipment is ordered, the paperwork goes out to sign, and a first-week plan is drafted for the manager to adjust.
Illustration with sample data
Example solution
A new client fills in one form. Missing details are flagged, a client record and folder are created, and a welcome email is drafted for you to approve.
Illustration with sample data
Example solution
Every customer in one place, with their history, open quotes and the next follow-up. The assistant drafts check-ins when a quote goes quiet, and you decide what gets sent.
Illustration with sample data
Example solution
Customers book from your website into the real calendar, reminders go out automatically, and changes are sent to you to confirm.
| Request | Priority | Assigned |
|---|---|---|
| Billing question | Normal | Office |
| Equipment fault | High | Field team |
| Change of address | Low | Office |
Illustration with sample data
Example solution
Requests from email, phone notes or a web form land in one queue. The assistant sorts them by type and urgency and suggests who should take each one, and your team works from a single list.
Most of these started as one annoying job. Tell us yours.
