u/ABHISHEK7846

About a few months ago I kept hearing the same story over and over from the small business owners I was talking to: a lack of tools was rarely the problem; they just didn’t have the time to stitch them together. I was talking to a man who was literally going through his contact form submissions by hand, every day, to weed out actual leads from spambots and then individually typing out responses.

That, ultimately, was why I began building Pushable. You describe a workflow in plain English, like you would to a new colleague joining your team, and Pushable sets it up and executes it automatically from then on, plugged into the tools people already rely on.

Here’s a short history of how it unfolded:

I began building way more than I’ll ever need - agent memory, OAuth, the full platform – before narrowing it back down.

I then pared it back to the bare minimum: “Describe the task, it runs the task.” This removed a ton of pressure on the build and pitch.

We recently acquired our first paying customer. He’s the man checking his inbox by hand; now he uses a chat agent on his website to achieve this. The time between sending leads and getting responses now stands at milliseconds, as opposed to a day or two.

I found the pricing conversation far more surprising than the technology. Instead of a flat subscription, I opted for credits-per-task, since it directly correlates with value delivered, as opposed to charging for access to an unused dashboard. Time will tell how this fares with additional customers.

So far, one paid customer, and a few other promising leads. Still very early on, but that feeling of, “Someone’s actually going to pay to avoid doing this task themselves,” is very different than, “That is a neat project.”

I’m available to chat more about the pricing strategy, automation space, or whatever else is on your mind- what strategies have you found effective in transitioning from one paying customer to the next?

For a time I kept seeing the same thing when I talked to small businesses. They had too many tools, not too few. Someone was manually copying leads from a form into a spreadsheet. Someone else was checking a Slack channel every hour just to forward messages along. It was not work it was just boring and repetitive and it took up a lot of time.

So I started building Pushable. The idea is simple - you tell it what you want done, in plain language, like you're explaining a task to a new coworker, and it sets up the routine and runs it on its own from then on. No workflow builder to learn, no code. It just plugs into the tools you already use — Gmail, Sheets, Drive, Slack - and handles the boring part.

Last week we got our first actual paying customer. He's running the agent as a chat bubble on his website, handling conversations that used to go straight to his inbox. Small win, but it was the first time it really hit me that this wasn't just something I found interesting to build — it was something someone was willing to pay for.

Some honest stuff from the process:

• The "just describe it in plain language" part sounds simple, but getting it to reliably interpret vague instructions took way more iteration than I expected
• I overbuilt this early on - started with agent memory, OAuth integrations, the works - before realizing the actual wedge was way simpler than I was treating it
• Pricing was its own headache. I landed on credits-per-completed-task instead of a flat fee, still not fully sure that's right long-term

Still very early days - one paying customer, a few others trying it out. Posting this mostly because I've gotten a lot out of reading other people's build threads here and wanted to pay that forward.

Happy to answer anything about the build, the automation space, or how it works.

Like a lot of people here, I've spent way too many hours wiring up automations — and even more time re-wiring them every time something small changed. The logic was never the hard part. The hard part was translating "just save the invoice and log it" into a chain of triggers, filters, and field mappings.

So I built Pushable to skip that step. You describe the task the way you'd explain it to a new coworker — "Whenever I get an invoice by email, save it to my Drive and log it in my spreadsheet" — and it figures out the steps and sets up the routine itself. No nodes, no canvas, no manual field-matching.

A few things that matter if you've used Zapier/Make/n8n:

• It connects to the usual stuff — Gmail, Google Sheets, Drive, Slack, and more.
• Routines run on a schedule or react to events (new email, new row, etc.).
• It ships with zero preset rules. You define everything in plain language, so it bends to your workflow instead of you learning its UI.

Here's a short demo of me setting one up start to finish:

Genuinely curious what the people here think — especially the n8n/Make crowd, since you know where the rough edges in this space usually are. What's the one repetitive task you'd throw at something like this first? Happy to try to build it live and report back.