PHAI · automation studio · bots, workflows, social dataPHAI · automation studio
PHAI builds the bots, workflows and data pipelines that do your repetitive work: posting, replying, pulling the numbers, writing the report. We run them for you, every night.PHAI builds bots and workflows that do your posting, replying and reporting, and runs them for you.
None of this needs a person. For now, it has one.
Each task becomes a job. We build it and keep it running, every night.
06:00Business runs 24 hours a day. People don't.
What PHAI builds.
[01]The shift
Pick what your team still does by hand and the board lights up those hours. Flip the switch to see the same week with a machine on it.
Rough hours for a small growth team with one person on each task. Office hours here are Monday to Friday, 9 to 18, and a full-time job is 40 hours. The audit gives you your real number.
[02]Night log
Every line is a job that used to eat someone's evening. Data comes in from eight platforms, lands in one of six places, and the log waits for you in the morning.
08
Platforms in
Sample summary: 08:12:46morning.summary36 jobs2 patchedsent · telegram
Orange means a platform changed something and the machine got patched.
06
Where it lands
[03]Services
Four kinds of machine. We design them, build them and keep them running after they ship.
[01]
Replaces
Repetitive work, handed to a machine.
We write down how the work is done by hand, then build the thing that does it instead: a browser or API script, a scheduled job, a bot that posts, replies and reports.
Delivers
[02]
Replaces
Fits the tools you already use.
Internal tools, dashboards and background services that plug into your CRM, your messengers and the APIs you already pay for. Web, desktop or mobile, often from one codebase.
Delivers
[04]
Replaces
Passwords, access and uptime, taken seriously.
Each machine gets only the access it needs, no password sits in plain text, and an alert fires when something breaks. When a platform changes its API, we fix the machine.
Delivers
[04]Process
Three stages. You get a written map before we build, a dashboard before we finish, and a team on call after.
Day 0
One call, then a written map: what goes in, what comes out, where it breaks, what to automate first.
map · agreed before the build
Week 1
A working version early, then short rounds of fixes. You see logs and a dashboard in the first week.
dashboard · live
Every night after
We deploy it, watch it and keep it alive. When a platform changes its API, we patch the machine.
monitor · on
[05]Team
A developer, a security engineer, a manager and a designer. You talk to the person who actually builds your machine, and the same four keep it running after it ships.
Co-founder, software developer
Co-founder, manager
Security and software engineer
Digital and visual designer
[06]FAQ
Anything a person repeats by hand.
Posting and replying on social platforms, pulling data out of them, moving records between tools, writing reports, approving things, sending reminders. We build the browser and API scripts, the Telegram and Discord bots, the scheduled jobs, and a dashboard so you can watch them work.
Yes, and the workflows behind them.
A bot on its own is rarely the whole job. Usually there is a scheduled task, an approval step, a report or a scraper feeding it. Moderation, member checks and alerts are the usual asks.
Eight: X, Telegram, YouTube, TikTok, Discord, Instagram, Facebook and LinkedIn.
Plus most public and partner APIs. The data goes wherever you already look: a dashboard, a spreadsheet, your CRM or a Telegram alert.
Each machine gets only the access it needs.
Access goes through accounts you control and can revoke, no password is stored in plain text or passed around, and every system we ship writes logs you can read.
We patch the machine. That is part of running it.
Every system we ship is monitored, so when X, TikTok or anyone else changes an API, an alert fires, we fix the adapter and redeploy, and the log shows what happened. You do not pay for a new project each time a platform moves.
Yes, a large share of our work.
For Web3 teams that is campaign, community and KOL tracking across X, Telegram and Discord. For games it is live social data pulled into the game itself.
Yes. Audit first, then fix or rebuild.
We write down what the existing scripts, bots or pipelines actually do, fix what keeps breaking, and rebuild only the parts nobody can maintain.
A brief, a reply, a short audit.
Send a brief through the form or message us on X. An engineer reads it and replies. If it looks like a fit, we do a short audit of the workflow and come back with a proposal: what we would build, how, and what you get first.
[07]Contact
Tell us what you still do by hand. An engineer reads it and replies on X or by email.
What happens next