Most requested
This is usually where it starts.
These eight situations are the ones companies describe to us again and again, across very different industries. Some are solved by automation, some by an internal tool, some by a product written from scratch. For each one we've written how it runs today, what a system can take over, and what has to stay with a person.
01 · Operations automation
Collecting requests from every channel
Requests from email, the web form, WhatsApp and the phone arrive in one flow.
How it usually runs today
Requests come from four places. The web form lands in an inbox, WhatsApp lives on one phone, callers are written in a notebook, and someone else sees the Instagram message.
Where the time goes
- By the end of the day it still isn't clear which request was answered
- The same person writing on two channels becomes two separate records
- On busy days the queue lives in the memory of whoever looked last
What a system can take over
- Every channel feeding one list
- Repeat records merged onto the same person
- Queueing by subject and urgency
- A reminder for anything left unanswered
What stays a human decision
What to actually say. The system prepares the queue and the context; the reply is still written by a person.
What gets recorded
- The channel and time a request arrived
- Who it was assigned to
- Time to first reply
- Why it was closed
Typical connections
- Email (Google Workspace or Microsoft 365)
- Web form
- WhatsApp Business
- CRM or the spreadsheets already in use
What gets delivered
- One request list and status screen
- Channel connections
- Assignment and reminder rules
- A weekly summary
The result: One screen: how many requests arrived today, how many were answered, which are waiting and with whom.
02 · Operations automation
Quotes, applications and records
The steps from request to quote run in order, and approvals and revisions are recorded.
How it usually runs today
The quote is copied from a Word file, the pricing sits in a spreadsheet, and approval is an email to someone. After the third revision nobody is sure which version was sent.
Where the time goes
- Which version went out last is unclear
- A quote waiting for approval appears on nobody's screen
- The same details are typed into the quote, the contract and the accounts separately
What a system can take over
- Drafting the quote from the request
- Version and revision tracking
- Routing the approval step to the right person
- Passing an accepted quote into records and invoicing
What stays a human decision
The price and the scope. The system prepares the draft and the history; what gets offered is decided by the team.
What gets recorded
- Every version and who changed it
- Approval and rejection times
- When it was sent and opened
- The final agreed scope
Typical connections
- Email and calendar
- CRM
- Accounting or bookkeeping software
- Electronic signature, where it is needed
What gets delivered
- Quote template and generation flow
- Approval steps and permissions
- Version history
- Status screen
The result: Where each quote stands, who it is waiting on, and which version was sent — all in one place.
03 · Operations automation
Appointments and reminders
Scheduling, confirmation, changes and reminders run on their own.
How it usually runs today
Appointments are taken by phone and written into a calendar by hand, so a change has to be made in two places. In the evening someone sends the reminders one at a time.
Where the time goes
- The calendar and the real situation drift apart
- A missed reminder turns into a missed appointment
- Changes and cancellations are not written down anywhere
What a system can take over
- Available times generated from one calendar
- Confirmation and change notifications
- Reminders going out on time on the chosen channel
- Flagging a no-show and offering a new time
What stays a human decision
Who is seen and when. The system handles availability and reminders; the schedule is still the team's call.
What gets recorded
- When an appointment was booked and changed
- Reminders sent
- Cancellation and no-show reasons
- Rescheduling history
Typical connections
- Google Calendar or Outlook
- WhatsApp Business or SMS
- Web form
- Patient or customer records
What gets delivered
- Calendar connection and availability rules
- Reminder templates and timing
- Change and cancellation flow
- Daily schedule screen
The result: The day's schedule on one screen; reminders go out by themselves and changes are recorded.
04 · Healthcare
Patient enquiry system
Recording, qualifying and routing enquiries to a coordinator, for clinics.
How it usually runs today
Patient enquiries arrive on Instagram, on WhatsApp and through the web form. International ones are in another language. The coordinator reads every one to work out which will actually become an appointment.
Where the time goes
- Different languages and time zones make follow-up harder
- When the same patient writes on several channels the history scatters
- A slow reply sends the enquiry to another clinic
What a system can take over
- Enquiries collected into one record, with the history merged
- Language and subject tagging
- Filling gaps with a standard set of questions
- Routing to the right coordinator and tracking reply time
What stays a human decision
Anything clinical. The system handles the administrative flow only — recording, routing and follow-up. Clinical judgement stays with the doctor.
What gets recorded
- The channel, language and time of the enquiry
- Which coordinator it went to
- First reply and follow-up steps
- Whether it became an appointment
Typical connections
- WhatsApp Business
- Web form and email
- Calendar
- Clinic records or CRM
What gets delivered
- One patient enquiry list
- Qualification and routing rules
- Reply templates and follow-up reminders
- Coordinator screen
The result: The coordinator works from one screen: who wrote, in what language, when they were answered, what is next.
05 · Internal tools
Internal operations dashboard
One screen showing what stage the work is at and who it is waiting on.
How it usually runs today
The status of the work lives in three separate spreadsheets, and nobody is quite sure which copy is current. When someone asks, the answer comes from asking a person.
Where the time goes
- The same figure reads differently in different spreadsheets
- Who the waiting work sits with is invisible
- Reporting means gathering the numbers by hand every time
What a system can take over
- All work collected in one source
- Stage and owner tracking
- Flagging work that has waited too long
- Regular summaries generated on their own
What stays a human decision
Priority. The dashboard shows what is waiting; what gets done first is decided by whoever runs the team.
What gets recorded
- Every stage change and its time
- The person responsible
- Time spent in each stage
- Completion and cancellation reasons
Typical connections
- Existing spreadsheets (Google Sheets or Excel)
- CRM
- Email and notification channels
- Internal software (REST API or webhook)
What gets delivered
- Role-based operations dashboard
- Stage and permission structure
- Filtering and search
- Summaries and export
The result: One screen: which job is at which stage, who it waits on, and how long it has waited.
RelatedInternal tools and AI systemsAI-assisted internal tools
06 · Internal tools
Reading data out of documents
Fields in an invoice, a contract or a form are read, checked and written into your systems.
How it usually runs today
Invoices and forms are opened, read, and typed into a spreadsheet by hand. At a hundred documents a day that becomes a job of its own, and typing errors slip through.
Where the time goes
- Manual entry costs time and produces errors
- The error is only noticed later
- Going back to the original document is awkward
What a system can take over
- Reading the fields out of the document
- Checking format and expected range
- Sending doubtful fields to review
- Writing verified data into the target system
What stays a human decision
Approving the doubtful field. The system marks what it is unsure of and shows that part of the document; a person approves it.
What gets recorded
- The original document and the fields read
- Automatic check results
- Who corrected what
- When it reached the target system
Typical connections
- Email attachments or a file folder
- Accounting or ERP
- Object storage
- Internal database
What gets delivered
- Document upload and processing flow
- Field mapping rules
- Review screen and correction interface
- Transfer into the target system
The result: A document arrives, the fields come out, only the doubtful ones reach a person, and the rest is recorded.
RelatedInternal tools and AI systemsQuotes, applications and records
07 · Internal tools
AI-assisted internal tools
Classification, summarising and drafting — with your team still approving the result.
How it usually runs today
Long threads have to be read and summarised by someone. Incoming messages are sorted by subject by hand. Standard replies are written from scratch every time.
Where the time goes
- Reading and sorting eats the team's day
- The same reply is rewritten each time
- Subject labels vary from person to person
What a system can take over
- Classifying incoming text by subject
- Summarising a long thread
- Preparing a draft reply
- Finding the relevant passage in a document
What stays a human decision
Approval. The model produces a suggestion and shows what it is based on; sending and deciding stay with the team.
What gets recorded
- The suggestion and the text behind it
- Who approved or changed it
- How often it was changed
- Which version was used
Typical connections
- Email and messaging channels
- Document and file sources
- Internal database or search index
- A language model provider
What gets delivered
- Classification and summarising flow
- Suggestion and approval interface
- Reasoning and source display
- Measurement and feedback
The result: The team starts from a draft with a visible source rather than a blank page — and still approves it.
08 · Custom digital products
Custom portals and web applications
When off-the-shelf software doesn't fit the process, we build the interface.
How it usually runs today
Customers or partners call or email for every piece of information. The answers sit in a spreadsheet that nobody outside can reach. Off-the-shelf software was tried, and the process didn't fit it.
Where the time goes
- Every outside question interrupts someone inside
- Fitting the process to the software works by breaking the process
- Permissions and visibility can't be set the way they need to be
What a system can take over
- Outside users seeing their own status
- Application, request and document upload flows
- Role-based permissions
- Notifications and status updates
What stays a human decision
Approval and exceptions. The portal collects the application and the documents; the decision stays with you.
What gets recorded
- Who signed in and when
- Applications and documents sent
- Status changes
- Correspondence history
Typical connections
- Authentication and role management
- Internal systems over an API
- A payment provider, where it is needed
- Email notifications
What gets delivered
- Product definition, scope and interface design
- The portal or web application
- Admin screen
- Launch, monitoring and handover
The result: Outside users check their own status, and only the steps that need a decision stay inside.
Getting started
If one of these sounds like your week, there's something to talk about.
Tell us which step gets stuck. In the first call we work out together whether automation is worth it and where to start.
After you send the form
- A reply within two working daysWe read your message and suggest a time that suits you.
- A 30–45 minute discovery callA working session that maps the process, not a sales pitch. If it isn't a fit, we'll say so plainly.
- A written summaryAfterwards we put in writing what could be built, in what order, and within what scope.