Smart Order Capture
Product

Why we built smartordercapture

Phone automation has a trust problem and a design problem. We're trying to fix both, starting with a product that says no when no is the right answer.

The smartordercapture teamFoundersMay 12, 20266 min read
A person in business attire holding a smartphone — the legitimate phone-automation use case the post describes.

We didn't set out to build another automation tool. The category has plenty — Tasker on Android, IFTTT and Zapier on the web, a growing pile of "AI agent" wrappers that promise to drive your phone for you. The reason this one exists is that none of those answer a question we kept hitting: what should automation refuse to do, by design?

The shape of the problem

When phones got powerful enough to automate, two ecosystems showed up. The legitimate one — accessibility helpers, content-creator workflows, field-worker form-fillers, idle-game farming — needed a real tool. The illegitimate one — gig-delivery offer-acceptance bots, ticket-scalping tools, ad-fraud kits — was happy to use whatever the legitimate one shipped.

Most existing tools take the position that they're just a hammer; the nails aren't their problem. That's a defensible philosophical stance but a poor product stance, because it means everyone in the category lives under the same regulatory and Play-Store-policy risk. A tool that draws no lines also gets no benefit from drawing them.

What we're doing differently

We hard-code a denylist of Android package names the engine will not target. It's enforced at three layers: server-side at workflow save, in the marketplace review worker, and compiled into the Android app itself. That last layer is the load-bearing one — even with no network, even with a tampered server, the device refuses to dispatch UI actions against denylisted apps.

The list isn't a secret. It's open source within the APK. You can read it at /docs/denylist. We add to it as we learn about new misuse categories.

What we're not doing

We're not building gig-delivery automation. We're not building ticket-purchase automation. We're not building ad-fraud tooling. We won't, and you can verify that we won't by reading our shipped code.

We think this position is good for users, good for the platforms we interoperate with, and good for the small business case of being a long-lived company that doesn't disappear because Play Store pulled us under a policy review.

What's next

We're in open beta on Android with a 5-minute setup. The free tier is generous on purpose: three workflows, all triggers, all actions, local execution. We charge $9 a month when you outgrow it. No per-grab fees, no surprise upsells.

If this resonates, sign up. If you'd like to argue with one of these positions, our inbox is open: hello@smartordercapture.com.