Most of it still
happens by hand.
Because the process only exists in your head. I design it out of there and into something that runs without you.
Free · 50 minutes · one workflow
I read every application myself and reply within 3 working days.
Angel Chen — five years a data analyst, now designing how one-person businesses and small teams work.
01—The problem
You’re the only one who knows how any of it works.
Which means it only happens when you're there.
- By hand
- A lot of your week goes into doing things manually — calculating, sorting, moving things from one place to another.
- Never the same twice
- You redo the same thing every week, and it's never quite the same twice.
- All of it runs on you
- It's not one thing. Onboarding, invoicing, reporting, chasing people for information. All of it runs on you remembering.
None of that is a discipline problem. It’s what happens when a business grows faster than anyone had time to design it.
02—About me
The business is fine.
The work is not.
That sentence is where almost every conversation starts.
I spent five years as a data analyst. Most of that job is unglamorous — making sure a number can be traced back to the document it came from, and that whoever reads it can tell a fact from an assumption.
Now I do the same thing for how people work. Same discipline, different subject.
03—How I work
Nothing lives in the chat.
If you've tried to do something large with AI, you've probably watched it go well for twenty minutes and then quietly fall apart. That isn't a prompt problem — it's what happens when the whole job is held inside one conversation.
Break it into steps
One question at a time, never the whole thing at once.
Write the state out
Each step produces a document, not a message.
Source every input
Every figure knows which file it came from.
Keep the context clean
Nothing gets carried forward that shouldn't be.
The point is that when someone asks where did this number come from, there’s an answer. That’s the difference between work that reads well and work you can defend.
04—What it costs
Which one sounds like you?
The difference isn't really price — it's how far into your workspace you want me.
“I know roughly what needs doing. I just want someone who knows this to check my thinking.”
USD 100 / hour
Consulting
I advise, you execute. I read what you send me properly before we talk, and afterwards you get a written summary you can hand to someone else.
“I want it fixed, but I want to be in the room while it happens.”
USD 150 / hour · min 3 hours
Working sessions
We do it together, in your workspace. No fixed finish line — we stop when it's solved, not when a package runs out.
“I don’t want to touch it. Just hand me the finished thing.”
from USD 2,000 / project
Build
I build it and hand it over. A working first version in about three weeks, full handover in about six. You review the first version before the balance is due.
05—One project
One month of work, and the report was wrong.
Four sessions over three weeks. All remote, all on his machine.
- Before
- A month of work: every PDF, spreadsheet and system export he had, loaded into one chat, asking it to make sense of all of it at once. What came back read well. It was also wrong — and it was going to a valuer who would decide what his company was worth.
- What we did
- We started again, in steps. Three reports had to be compared, so we listed exactly where they disagreed and what each disagreement was worth. Then we went back through the evidence for what was missing — not what was wrong, what wasn’t there yet. Every figure ended up traceable to the document it came from.
- After
- A report he could stand behind, and a list of what he still needed to find. He never asked me to build him a system — he didn’t need one.
Currently building an internal operations system for a content brand — signed in early July, first working version delivered three weeks later.
06—In their words
What people say afterwards
Written by the people who worked with me, not edited by me.
“My Notion was like a storage room full of junk. Angel worked out what I actually needed and built something that’s genuinely nice to use — now I look forward to opening it.”
07—Fit
Is this for you?
If the week I described earlier sounded like yours, then probably yes — especially if the business itself is steady and what's missing is your time.
This probably isn’t you, if —
- You're looking for someone to teach you.
- I don't run courses. But tell me what you're trying to learn — I read every one, and it's how I decide what to make next.
- You want AI to run without you.
- It hallucinates, drifts when there is a lot of material, and will argue confidently for whatever premise you gave it. You stay the one who verifies your own facts — that is not a limitation, it is the design.
- Nothing in your business repeats yet.
- If the work is different every time, there is no process to design. Come back when it repeats.
- Your records are still on paper.
- I work with what's already digital. Getting it into a file is someone else's job first.
08—Practical
What working together looks like
- Time zone
- GMT+8.
- Language
- English or Mandarin.
- How we meet
- Google Meet. For hands-on work, TeamViewer on your machine.
- Your data
- Nothing leaves your computer. I don't take copies, I don't upload your files, and I don't need admin access to anything.
- Payment
- Wise. Consulting and working sessions are paid before we start. Build projects begin with a deposit, and you review the first version before the balance is due.
- Rescheduling
- 12 hours' notice is enough.
- After the call
- A written proposal within 3 working days. If I don't think I'm the right person for it, I'll tell you that instead, and say why.
09—Questions
Questions people ask
Start with a
conversation.
Free. 50 minutes. One workflow. I read every application myself and reply within 3 working days — including when the answer is no.