melonjuice.ai · Sectors · Insights · How we work · FAQ · Contact

Frequently asked questions

These are the questions firms most often ask before working with us, answered plainly. For the full picture of how a project runs, see how we work.

What we build

What does melonjuice.ai actually build?

Practical automations that take repetitive admin off people: connected workflows, AI assistants that read documents, draft replies and triage requests, and integrations that pass one update to every system it should reach. An automation can prepare, sort, draft, chase, file and flag. Your team decides.

Which sectors do you work with?

We focus on accountancy, recruitment, freight and logistics, law firms and letting agents. The same approach applies elsewhere, so if your work isn't listed, ask.

What kind of task is a good fit?

A job that comes back every week, follows a recognisable pattern and mostly involves reading, typing, chasing or copying information between systems. Document chasing, inbox triage, status updates and re-keying data are typical. Our insights show worked examples for each sector. The examples in them are illustrative, not client results.

Is a small firm too small?

No. A five-person firm with one painful process is as good a starting point as a larger operations team.

Human review and control

Does a person check what the automation does?

Yes. Early on, every outgoing message or system update can be held for a person to approve, so you can see exactly what the automation would do before it does it. Sensitive steps keep a human sign-off permanently.

What won't you automate?

We won't build automations that make professional judgements such as tax treatment, legal advice or whether to act for a client; approve pay, refunds or payments without a person signing off; make safety decisions; carry out identity, right to work or anti-money laundering decisions in place of your staff or your chosen verification provider; or send anything in your name that you haven't agreed it can send.

Can we switch it off?

Yes. There should always be a simple way to pause it, and the handover document explains how.

Tools and systems

Which tools can you connect to?

We work with tools that have an API or an export. What can be connected depends on the product, your licence and how you use it. If something can't be connected, we say so when we agree the scope rather than discovering it later.

Do we need to replace our existing tools?

Usually not. Most of the work connects and automates the systems you already pay for. Where a tool can't be connected, we'll tell you before we start.

Data

What will the automation be able to access?

For any workflow we propose, we'll tell you which mailboxes, folders, systems and records it accesses and with what level of permission, where data is processed and stored, which third-party services are involved, whether an AI provider can keep or train on your data, how long anything is kept, who can see the logs and how to switch it off.

How do you approach data protection?

We design around least-privilege access, keep humans in the loop for sensitive steps and document where data flows. We don't claim certifications we don't hold. If your firm has its own data protection or IT requirements, we work to them.

Cost and timing

How much does it cost?

There is no public price list. Each project is scoped individually, because the cost depends on the workflow and the systems involved. We agree the scope and the cost with you in writing before any build work starts.

How long does a project take?

It depends on the workflow and on access to your systems, so we don't promise a number of days here. Scope, risks and owners are agreed before a build, and the first system stays small until it proves itself.

What happens after handover?

You get documentation your team can follow, logging and alerts. Ongoing support or changes can be agreed separately if you want them.

Getting started

How do we start?

Email us with a short description of the task you'd like to get rid of. We'll reply to say whether it looks like a fit and suggest a call if it does.

Do you publish case studies?

Not at the moment. We'd rather not publish anything we can't stand behind, so the examples on this site are illustrative, not client results.

Email us or write to luke.sewell@melonjuice.ai, or use the contact form

Background reading: How we work · AI automation by sector · Insights