Example package
Report fetcher
One portal's reports downloaded and filed on a schedule.
You get
- Steps agreed in writing
- Scheduled runs with logs
- Files named and filed
- Failure alerts
Sound familiar?
What we hear from businesses before a project like this starts.
- Someone spends hours a week downloading reports from supplier or carrier portals.
- We re-type the same data into a portal that has no import or API.
- An RPA platform licence costs more than the task it automates.
- Our old desktop or web system can't be replaced but nobody wants to use it.
- A previous bot breaks every time the site changes and nobody notices.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
Reliable login and navigation
Sessions, two-factor handled the way your policy allows, and waits that follow the page, not set timers.
02
Downloads and uploads
Reports and files fetched, renamed and filed where your team or another system picks them up.
03
Form filling from your data
Records entered from a spreadsheet, database or CRM, with a check that each one saved.
04
Run logs and screenshots
Every run recorded so you can see exactly what the bot did.
05
Stop on surprises
Unexpected pages or errors pause the bot and alert a person.
Tools that come up most: Playwright, Python, Node.js, Selenium, Power Automate Desktop where already licensed, Docker, cron or Cloud Scheduler, Google Drive, SharePoint and email.
What you get
Concrete pieces, each one something you can open and check when it's done.
Report fetchers
Scheduled logins that download and file reports.
Playwright, schedulerData entry bots
Records entered from your source of truth, with confirmation.
Playwright, your data sourcePortal monitors
Checks for new documents, statuses or messages, with alerts.
Scheduled checks, notificationsHand-off to other systems
Downloaded data parsed and pushed to a sheet, database or app.
Parsing, APIsBot rescue
An existing brittle bot rebuilt with better selectors, logs and alerts.
Review, rebuildTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Data entry bot
Records entered into a portal from your data, with confirmation.
You get
- Field mapping agreed
- Entry with save checks
- Exceptions list for a person
- Run log with screenshots
Example package
Bot rescue
An existing automation made dependable.
You get
- Review of current bot
- Rebuilt steps
- Logging and alerts
- Runbook
How we approach it
The habits that keep this kind of project from going wrong.
1
API first
If the system has an API or export, we use that instead; a browser bot is the fallback, not the default.
2
Within the site's terms
We automate sites you have accounts on and the right to use this way, and we don't bypass security checks.
3
Your credentials stay yours
Logins are stored in your secrets manager or server, not in our hands.
How we work
A written scope first, then working progress you can check, then a proper handover.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- How many portals and steps
- Login and two-factor method
- How often the sites change
- Where results need to go
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
Questions people ask first
Isn't this what UiPath does?
Yes, for many tasks. For one or two portals, a Playwright bot on a small server usually does the same job without a platform licence.
What about captchas and bot checks?
We don't build bots to defeat them. If a site challenges automated logins, we look for an API or export, or ask the vendor for access.
What happens when the website changes?
Runs stop and alert instead of entering bad data. For 30 days after handover we fix anything we built that stops working as scoped, at no charge.
Where does it run?
On a server or cloud account you control, on a schedule we agree.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com