Admin panels and back offices
Search, edit and manage your data with screens designed for your team, instead of a generic database tool.
Copying data between systems, chasing approvals, building the same report every Monday. We replace that work with internal tools and automations that run reliably in the background, with a person in control wherever judgement is needed.
How an automation runs
Trigger
A schedule, an incoming email, a webhook or a button in the admin.
Gather
Pull the data from the systems involved, with every source recorded.
Process
Apply your rules, or let AI classify, summarise or draft where rules fall short.
Check
A person approves anything that sends, spends or can't be undone.
Log and report
Every run is logged, failures alert someone, and results land where the team works.
Tools for the work behind the scenes, built around how your team actually works.
Search, edit and manage your data with screens designed for your team, instead of a generic database tool.
Requests, reviews and sign-offs with notifications and a clear audit trail of who approved what, and when.
Syncs, reminders, clean-ups and reports that run on time, with a dashboard that shows every run and every failure.
Incoming email matched and sorted, lifecycle emails triggered by what users do, and documents assembled from your own data.
Research, classification, summaries and drafts done by AI and checked by a person before anything goes out.
Dashboards and scheduled reports that pull from all your systems, so nobody has to build spreadsheets by hand.
Our products run a long list of scheduled jobs: syncing inboxes and marketplace orders, refreshing tokens, sending lifecycle emails, sweeping abandoned checkouts and checking backups. Admin back offices cover billing, users, AI jobs and sales, and a job dashboard shows every background task and its status.
Even the dull admin is automated. Postcrest syncs its Stripe invoices, payouts and fees to Moneybird from a bookkeeping dashboard, and prepares the evidence for payment disputes so a person can review it before it's sent.
A few of the jobs running in our products
Every 15 seconds: publishing queue
Scheduled social posts picked up and published on time.
Every 5 minutes: inbox sync
Mailboxes mirrored, replies matched and classified.
Every 10 minutes: orders and checkouts
Marketplace orders imported, abandoned checkouts released.
Every 15 minutes: token refresh
OAuth tokens renewed before they expire.
Weekly: backup check
An automated check of the database backups.
Planning, scheduling and order handling that now depend on spreadsheets and people remembering things.
Incoming requests sorted, enriched and routed, with drafts ready for a person to send.
Invoices, payments and bookkeeping synced automatically, with exceptions flagged instead of hunted down.
Research, follow-ups and CRM updates handled in the background, with a person deciding what goes out.
Start with the task that costs the most time, prove it works, then do the next one.
We map where your team spends time on repetitive work and which tasks are worth automating first.
Decisions, exceptions and anything customers see get a review step.
Start with the one task that saves the most time, live early and improved together with your team.
Integrations with the tools you already use, so nobody types the same data twice.
Every run is visible: what happened, when and why, with an alert when something fails.
Automate the next task once the first one has proven itself.
Internal tools run on the same stack as our products: admin screens in Rails, background jobs with a dashboard, and AI only where it beats a simple rule.
Automating one well-defined task is a small project. These factors decide the estimate:
It depends on the number of processes, the systems involved and how many exceptions there are. After a free intro call you get a written scope and estimate, usually starting with the task that costs your team the most time.
That depends on the process and the systems involved. We start with one task, get it live early and expand from there. The estimate after the intro call includes a timeline per phase.
Repetitive, rule-based work that happens often: copying data between systems, sending reminders, building reports, sorting incoming requests. Rare work that needs a lot of judgement is usually better left to people.
Only where it beats a simple rule: reading messy email, classifying requests, summarising or drafting. For everything predictable, plain code is cheaper and more reliable.
For small, simple flows they're fine. When a process is business-critical, high-volume or full of exceptions, a built tool with tests, logs and proper error handling is more reliable, and often cheaper over time.
Yes. We add review steps for anything that sends, spends or can't be undone, and every run is logged, so you can see exactly what happened.
A CRM shaped around your sales process, with lead enrichment, verified contacts, AI drafts, human approval and reply handling.
Read moreReliable connections between your tools: payments, bookkeeping, social networks, marketplaces, Google services and AI providers.
Read morePractical AI inside your processes and product: email and document handling, classification, drafting and agents, with people in control.
Read moreTell us about the repetitive work in your week. You'll get an honest view on what's worth automating and what it would take.
Typically a reply within one business day.
Useful to mention