Describe one recurring task
Choose a task that happens weekly or daily rather than an entire department. Explain the input, the expected output, the person currently responsible, and the point where it becomes slow, repetitive, or unreliable.
Let’s talk
Tell us
what sucks.
Tell us what keeps getting copied, chased, forgotten, or done twice.
A real example is more useful than a perfect brief. Share the tools involved, recurring task, and what you would like to change.
Not sure where to start?
Start with a free workflow audit. We focus on one process and work out the next useful step.
The short version
Before
you send.
Should I include customer records or passwords?
No. A short description of the process and tools is enough. We can arrange an appropriate access method if the work progresses.
Can I ask about a project outside lead automation?
Yes. Describe the recurring work, what triggers it, and where it breaks. We assess the fit before suggesting a scope.
Does sending this commit me to a project?
No. It starts a conversation. Scope, pricing, permissions, and payment are agreed separately.
Useful details.
No perfect brief required.
- Where the task starts
- Which tools it touches
- Who owns the next action
- What keeps going wrong
- What a useful improvement would change
Preparing a useful project conversation
Bring the messy version.
That is the useful one.
You do not need a technical brief to contact Bad Clause. A recent example of the work is more valuable: what started it, which tools were involved, who touched it, where it waited, and what happened next.
Do not send passwords, API keys, customer databases, medical records, financial records, or other sensitive material through the form. A short description is enough to decide whether a deeper conversation is appropriate.
Name the systems involved
List the form, inbox, spreadsheet, CRM, calendar, support desk, messaging account, database, or internal tool involved. It is fine if you do not know whether those systems have APIs; that is checked during discovery.
Share the operating impact
Useful context includes delayed response, incomplete records, duplicated work, avoidable support time, reporting delay, missed follow-up, or reliance on one person. Approximate frequency is more useful than an inflated claim about hours saved.
Explain the decision boundary
Tell us which steps follow clear rules and which require experience, approval, or professional judgment. This helps determine whether the first solution is a simple workflow, an AI-assisted step, or a process change without automation.
A likely fit
The workflow repeats, somebody owns it, examples are available, the business can provide legitimate access, and there is a measurable reason to improve it. Strong first projects usually have a visible handoff, a known source of truth, and enough volume for a change to be observed within a practical pilot period.
Probably not a fit yet
The goal is simply to add AI, the process changes every time, nobody can approve the rules, the required data cannot be used legitimately, or the expected benefit does not justify implementation and support.