pedrojimenez.dev
// for small business

The weekly manual work should run itself

Answering the same WhatsApp question forty times a week, posting the same promotion to four platforms by hand, retyping the same numbers into the same spreadsheet — none of that is a staffing problem. It is an automation problem, and it is usually a few days of work to remove permanently.

Start a projectBook a 20-min call
// what almost nobody tells you

Automation doesn't replace your team. It stops paying them to copy and paste.

Every task someone does the same way each week — forwarding, reformatting, posting, reconciling — has a cost nobody writes down, because it arrives in minutes. Added up, it's almost always more than it would cost to make it run by itself. Good automation is invisible: one day that task simply stopped existing.

// before and after
× Today✓ With the build
Today: One promo: design it, write four versions, upload to four networks.
With the build: One idea in Telegram → image and copy for four networks, one tap to publish.
Today: WhatsApp answered whenever someone has a minute.
With the build: Instant answers from your own prices and documents.
Today: Numbers copied by hand from one system to another every week.
With the build: A pipeline that reconciles on a schedule.
Today: When something breaks, nobody knows until a customer complains.
With the build: Fallbacks at every step: an outage degrades instead of breaking.
// the cost of doing nothing

Put in your numbers.

$390 a month
paying for work a machine could do
Calculated with your numbers, not ours. It isn't a promise — it's the size of the problem.
// how it works
01

Map the task

What comes in, what goes out, who does it today and how often.

02

Build the pipeline

A bot or a scheduled job, wired to the tools you already use.

03

Run it with guardrails

A daily cost cap and a fallback at every external call.

04

You just approve

Review the result and publish in one tap — or let it run on its own.

// what gets built
01

A bot that knows your business

WhatsApp answering from your actual documents and prices, not from a generic script — with a real handover to a person the moment the question needs one, and the bot going quiet as soon as someone takes over.

02

Post once, publish everywhere

One message in, per-platform copy and imagery out, published to Instagram, LinkedIn, Facebook and X in a single tap.

03

Costs that track intent

The expensive AI model runs only when the job actually needs it. On the social bot that is roughly nine cents for a designed promo image and about a penny for everything else, with a daily cap so a bad day cannot become a bad invoice.

04

Fails soft, never silent

Layered fallbacks at every external call, so a provider outage degrades the output instead of taking the whole thing down.

05

Yours to tune

Models, prompts, brand voice and API keys editable from an admin console — changing how it writes is a form submission, not a redeploy.

// do you need it?

Tick what happens to you today.

0 of 5
You probably don't need this yet — and that's worth knowing.
// the proof

Running in production on a single server: a Telegram bot that turns a photo or a one-line idea into four ready-to-publish social posts, at roughly $15–20 a month all in.

Social Command Center — Automation · AI
Automation · AI · 2026

Social Command Center

Telegram bot that turns a photo or a one-line idea into ready-to-publish social posts — per-platform copy, AI images with correct on-image text, and one-tap publishing to Instagram, LinkedIn, Facebook, and X.

Read the case study →

What does your team redo every week?

If the answer is anything repetitive, it can probably run itself. Describe it and you will get an honest read on whether it is worth automating.

Start a projectBook a 20-min callAll work

Services