You keep the keys.
Your accounts. Agreed access. Human approval where it matters.
Bad Clause / AI & business automationLess corporate. More useful.
Busywork
can get
lost.
The task nobody should be doing.
Your people weren’t hired to copy, paste, chase, repeat. We build AI and automation that gets that work out of their way.
Find the bad clauseExhibit A / your average workday
“Just following up.”“Can you update the sheet?”“Who’s handling this lead?”“Let’s circle back.”
That’s not
a workflow.
It’s a hostage
situation.
Somewhere between your inbox, CRM, and fourteen open tabs, the actual work got lost.
Bad Clause finds the repetition, sorts the handovers, and builds a system that does not need chasing.
Meet your bad influenceWhat we actually do
Less “AI strategy.”
More shit done.
Useful automation. Connected tools. A human in charge.
Our suggested first offence
The lead
came in.
Don’t ghost it.
Start with one workflow: new enquiry useful reply clear owner booked conversation.
No company-wide transformation circus. A focused pilot, with a before, an after, and a decision.
Fix the follow-upSound familiar?
Different business.
Same old bullshit.
Bad clauses.
Rebellious. Not reckless.
Break the habit.
Not the business.
Failures don’t get buried.
Defined exceptions, visible alerts, and somebody responsible for the next step.
The numbers get a vote.
A baseline, a bounded pilot, and evidence before we suggest doing more.
What changes after the build
The owner is obvious.
Every event has a person, a queue, or a documented next action.
The exception is visible.
Failures stop hiding in inboxes and silent integration logs.
The result can be checked.
The baseline and operating cost sit beside the claimed benefit.
Field notes / no thought-leadership cosplay
Be suspicious.
Ask better questions.
AI automation agency / India + remote
What business automation is
supposed to fix.
Bad Clause is an independent AI automation agency for service businesses that have outgrown manual follow-up, disconnected tools, and work that depends on somebody remembering the next step.
We design business process automation around a real operating problem first. AI is used where interpretation, classification, drafting, or retrieval adds value. Predictable steps stay predictable. High-consequence decisions stay with people.
Find the operational leak
The first job is not choosing a model or automation platform. It is tracing where time, context, leads, or accountability disappear. We examine the trigger, the people involved, the systems touched, the normal path, and the exceptions before proposing a build.
Design the workflow before the agent
A useful automation has an explicit beginning, state, owner, and end. It knows what information is required, what can happen automatically, what needs approval, and how a person takes over when the input is incomplete or the system fails.
Connect the tools already doing the work
Forms, inboxes, calendars, CRMs, spreadsheets, messaging channels, support desks, and reporting tools often hold different pieces of the same process. We connect only the systems needed for the first measurable workflow rather than creating a bigger software estate.
Operate it after launch
Production automation needs monitoring, logs, access ownership, usage-cost visibility, change control, and a manual fallback. The build is only credible when your team can see what happened, correct an exception, and understand who is responsible for maintenance.
A useful first automation project
Choose work that happens frequently, follows a recognisable pattern, has a named owner, and produces an outcome you can measure. Lead response, CRM handover, support preparation, recurring reporting, and document routing often meet those conditions.
A bad first automation project
Avoid starting with a company-wide AI transformation, a process nobody can explain, or a high-risk decision with no review path. Automating confusion creates faster confusion and a maintenance problem with a monthly invoice.
You don’t need another deck.
You need
less of this.
Tell us what gets copied, chased, forgotten, or done twice.
Let’s kill the busywork