Someone at your company is doing by hand what a system would do on its own.
Data that leaves one place and gets typed into another. A spreadsheet only one person knows how to open. An order that goes through three approvals over WhatsApp. A long contract someone rereads every time a question comes up. A question that arrives 40 times a week and always gets the same answer.
Each of those costs hours a week, and the full bill only shows up when the person holding it all together takes a vacation.
Software that automates the repetitive part and gives the hours back.
- An internal tool. A screen where your team does the work, instead of the shared spreadsheet nobody is allowed to break.
- A job that runs on its own. The report goes out every Monday, the invoice goes out on the due date, the reconciliation happens overnight — with nobody remembering to do it.
- Systems that talk to each other. An integration between the ERP, the spreadsheet and the WhatsApp your company already runs. What gets sold in one place shows up in the other without being retyped.
- Data gathered in one place. A job pulls what is spread across several systems, cleans it and builds the report someone used to assemble by hand.
- An answer after hours. An agent answers the usual questions on the company's behalf, and fetches a person when the question is new.
- An answer drawn from your documents. An agent answers from the contract, the manual or the price list, and points to where the answer came from. It is the shape that usually goes by the name RAG.
- Yours, not ours. Code, accounts and hosting are in your name from the first day.
None of this is off the shelf. It is built on top of what your company already uses — the ERP, the spreadsheet, WhatsApp, the flow someone set up in n8n, Make or Zapier. What goes in is agreed in writing before it starts.
It starts with what is done by hand today. The price comes after the scope.
You tell us what someone does by hand today — who does it, how many times a week, and what happens when it goes wrong. We ask where the data lives and who needs to see the result. Once nobody has a question left, that becomes a document with what the system does, with which data, and how you will know it worked.
Only then do we talk about price, and the number arrives with the proposal. Weeks, not months — and no clock starts before you agree.
If it is in the scope, the system does it.
You use the system with the document beside it. If anything described in it isn't working the way it was written, it is corrected at no cost. The scope also says how everything described in it is checked — it is the same document that defines when the work is done.
The document also marks where the guarantee stops. Later you may want a new report, another system connected or a rule changed. None of that was in there. Then we write another scope, with another price.
We have built this before.
- An audio news reader. Pulls new articles every 20 minutes, turns the text into speech and builds one audio file from the ones you pick.
- An online menu for a small restaurant. On the restaurant's own domain, with orders over WhatsApp, PIX on the spot, a fee per neighbourhood and a courier called from the panel.
- Staff rosters by branch. The manager builds and publishes the roster, approves shift swaps, and staff clock in from a phone with their location.
- Goals per cycle for teams. Each objective becomes measurable results, progress goes in at every check-in and the reminder arrives every week.
- Video hosting for course sellers. Its own player that only plays on the authorised domain, and a plugin that drops the lesson into any WordPress page.
- A dating app by music taste. Sign in with Spotify, swipe through profiles ordered by affinity and chat in real time with a match.
- A CV editor. Assemble it by dragging sections, pick a template, adjust the style and download the PDF on the spot.
- A podcast produced with nobody recording. Picks the news, writes the script, narrates it in a synthetic voice, uploads the audio and updates the feed.
- A brokerage account run by a program. Simulation on by default, a volume cap per order and every attempt written to a log.
- A condominium management platform. Common-area bookings with no clashes, maintenance tickets and notices that reach the resident's app.
- An intermittent-fasting app. Times the fast, takes protocols you define yourself, reminds you when to start and stop, and keeps a history of every one.
- A vocabulary app with spaced repetition. Works offline and syncs when back online, with reviews paced to how each word is forgotten.
Requests that fit in a scope.
None of these was commissioned. They are examples of the size of work we do, written the way a request would arrive.
- A distributor. Orders arriving over WhatsApp land on one screen, and the stock check runs overnight.
- A car repair shop. A work order opened on a phone, with photos and parts, and the customer told when the car is ready.
- A language school. Attendance per class, overdue fees on screen, and the reminder going out on its own.
- A shop with after-hours service. Answers the usual questions, books appointments, and hands the rest to a person in the morning.
Describe the task in a paragraph.
Who does it today, how many times a week, and where the data lives. That is enough for a first answer.
What we do with the message is on the privacy page.
hello@30labs.com.brTaking on work · 2026