Service 05 / Automation
The thing you repeat daily
shouldn't need a human
Scraping, tidying spreadsheets, copy-paste, cross-platform posting —
fixed rules, repeated daily, nothing accumulated at the end.
Give it to a script. Keep the judgement work for people.
Who this is for
- ·Every morning someone manually copies data from several sites into a sheet
- ·Content must go to several platforms and each one means pasting again
- ·You have scheduled jobs that fail silently and nobody notices
- ·Data processing has manual steps with high error rates and no traceability
Does this sound familiar?
「An hour a day on data tidying — 250 hours a year」
「Whether last night's job succeeded is only knowable by checking the output」
「Two people tidy the same data and produce different formats」
「The script needs parameters edited by hand, so it can't be handed to anyone else」
What you get
What I don't do
Stating the limits saves both sides more time than listing capabilities.
No ToS-violating scraping
No paywall bypass, no CAPTCHA solving, no hammering sites. If a target explicitly forbids scraping, I decline.
No automation of judgement
Automation suits fixed rules. Steps requiring subjective calls can be assisted, not fully automated.
I don't hold your credentials
For authenticated sources I use your APIs or short-lived tokens. Passwords never live in my scripts.
No promise that upstream never changes
Target sites redesign and scrapers break. Delivery includes 30 days of fixes; long-term care can go to a retainer.
Timeline and pricing
Fixed pricing, not hourly. Under $2,200: 50% upfront, 50% on acceptance. Above: three instalments. Third-party costs (server, API, domain) are not included.
Why take my word
This site submits to search engines automatically
A script runs as part of deployment, pushing all URLs to IndexNow and logging the response. I don't have to remember — that's the entire point.
Scraping and deduplication, actually shipped
The previous version ran RSS and API pipelines: multi-source fetch, cleaning, dedup, storage, notification. It also taught me what happens when a source changes structure and the whole batch dies.
Visibility on failure is non-negotiable
A pipeline that fails silently might as well not exist. Everything delivered includes failure alerts with cause and retry guidance.
Sometimes the answer is no
If the task takes five minutes a day, automating it costs more than it saves. I'll say so during process mapping.
Common questions
I can't code — can I maintain it?
The parts you maintain are configuration: source URLs, schedule, recipients. Those live in a config file. Logic changes need me or your developer.
Where does it run?
On your existing server, or a small dedicated machine. No new services to buy; typically tens of RMB per month.
Will scraping get blocked?
Rate limiting and header handling reduce the risk. If a target actively blocks, I won't fight it — an official API or a different source is more sustainable.
Can it have a UI with a button?
Yes, at higher cost. Most cases are better served by 'runs on schedule, alerts on failure' than by a manual button. If a UI is genuinely needed, it's quoted separately.
Describe the thing you repeat
Where the data comes from, how it's processed, where it ends up, how often. I'll say whether it can be automated, whether it's worth it, and roughly what it costs.
Describe the workflowOther services
Public pricing, written boundaries, and an honest no when it's not a fit. That saves more time than any promise.