I'm a one-person automation shop in Japan taking n8n and API integration work as white-label overflow. Your spec, your brand on the handover, and no contact with your client at any point.
Not a referral scheme, not a rev-share, not a partnership. Contract implementation work, billed flat.
The discovery call went well, the retainer is signed, and the build is now sitting in a backlog because the one person who can do it is already booked. That is the exact gap I sit in — one layer behind you, invisible to your client.
You sell automation-as-a-service or monthly builds. Demand is lumpy; a permanent second implementer is not justified yet. Buy the capacity by the job instead.
HubSpot, Salesforce, Zoho, monday.com, Shopify. You are strong on configuration and strategy; the custom API glue between systems is the part that keeps slipping.
Automation is explicitly not your service line, but clients keep asking for it. Take the work, keep the relationship, and hand the build to someone who does only this.
A developer has left, is on leave, or is stuck on a bigger project, and existing integrations still need to keep running. Short engagements are fine — there is no minimum commitment.
Implementation, not advice. Tell me what to build and I build it — from a spec doc, or from a call recording, a Loom and a Slack thread if that is all that exists.
Gmail, Google Calendar, Sheets and Drive APIs, Slack, Notion, Airtable, Discord, HubSpot, Stripe, GitHub, and REST and webhooks generally. If a tool is new to me I say so and quote the ramp-up honestly rather than hiding it inside a padded estimate.
Confidentiality. I sign your NDA — send it with the first brief. I do not need to negotiate it and I do not ask you to sign mine. Credentials are held only as long as the build requires and deleted on request; I prefer scoped service accounts to anyone's personal login. I do not paste your client's proprietary data into third-party AI services. I will not solicit or accept direct work from a client I met through you.
Japan is UTC+9, nine hours ahead of the UK. You brief me at the end of your day; I build during your night; there is something to look at when you open your laptop. For an agency under a deadline, an overnight cycle beats sitting in the same office hours.
A narrow window I actually keep, rather than a claim of 24/7 availability. That is 16:00–20:00 in Japan — the end of my working day, the start of yours.
Default is async: your Slack Connect channel, your Notion, or email. I adapt to your stack; you should not have to adopt a tool for a subcontractor.
On anything running longer than that. You should never have to ask where a build stands. If I am blocked waiting on access, you hear it the same day.
Kickoff for a complex build, or untangling a disagreement about a spec. Otherwise I would rather leave your calendar alone.
All figures in USD, excluding tax. Payment by Wise or PayPal, net 14. Per-workflow work is 50% to start and 50% on delivery; under $600 a single invoice on delivery is fine.
| Tier | Typical shape | Price | Turnaround |
|---|---|---|---|
| Simple | Single trigger, linear path, 2–4 services, light transformation. Form submission → enrich → CRM → Slack notification. | $500 – $800 | 2–3 business days |
| Standard | Branching logic, 4–8 services, an AI step, real error handling and retries, a small dashboard or log sheet. | $800 – $1,400 | 4–7 business days |
| Complex | Multi-workflow system, sub-workflows, custom Code nodes, an API or scraper component, staging and production, handover docs. | $1,400 – $2,000+ | 2–3 weeks |
Rush delivery on Simple and Standard is +50%. Anything materially above the Complex tier gets scoped and quoted individually rather than jammed into a bracket.
| Reserved capacity | Per month |
|---|---|
| ~20 hrs — 2–3 simple workflows, or one standard build plus maintenance | $1,000 – $1,500 |
| ~40 hrs — an ongoing build queue plus fixes on existing workflows | $1,600 – $2,400 |
| ~60 hrs — effectively a part-time embedded implementer | $2,500 – $3,000 |
Month to month. Either side can stop on 14 days' notice. No annual lock-in — I would rather you left than stayed because of a clause.
The honest position first: I have no completed client engagements to point at. This business has not yet delivered a paid build for an external client, and I am not going to invent one, anonymise one, or describe a personal project as if an agency had commissioned it.
What I can offer instead is code and output you can open right now, without an NDA, a login or a call — and decide for yourself how I name things, structure things and document things before you trust me with a client's portal. That, plus the $150 pilot, is the whole basis on which I am asking for a first job.
A Gmail triage workflow — messages classified by an LLM step and labelled by priority. Listed by n8n itself, so you can read the node structure and naming before briefing me on anything.
https://n8n.io/workflows/17365-label-gmail-emails-by-priority-with-groq-llama-33/Works out a form's fields, its options, and which CAPTCHA it uses (reCAPTCHA v2 or v3, Turnstile, hCaptcha) using plain HTTP and no browser at all. Built so a job can be judged feasible before anyone bills for the attempt. MIT licensed.
https://github.com/setlog-app/contact-form-reconA require-time hook that forces safe launch options and a concurrency limit across an entire codebase of browser automation scripts. The relevant thing for you: it is what I reach for when a fleet of existing scripts has to change and rewriting them all is not on the table. MIT licensed.
https://github.com/setlog-app/playwright-launch-guardScheduled-task console-window suppression, resource-exhaustion measurement, and screenshots of windows that are hidden behind others. The README states plainly that the first diagnosis was wrong and what the measurements actually showed. MIT licensed.
https://github.com/setlog-app/windows-automation-opsScores how often a brand is cited by generative search engines across 30 prompts and four metrics, and reports it. Written to make the numbers auditable rather than impressive; the README says outright that no ranking outcome is guaranteed. MIT licensed.
https://github.com/setlog-app/ai-search-visibility-auditThree iOS apps built with Expo and TypeScript; one was submitted to App Store review and rejected because a config plugin silently injected a background-mode declaration. This checks for that class of injection before the build goes up. MIT licensed.
https://github.com/setlog-app/expo-plist-auditThree 9:16 fifteen-second ads for one fictional product with three different hooks, playable in the browser with the intent, the process and the measured production time for each. Fully AI-generated and labelled as such. Included only because it shows finished output; it is self-initiated work, not a commissioned campaign.
https://setlog-app.github.io/ai-jidoka-lab/portfolio/What I do stand behind: if a delivered workflow does not do what the agreed spec says, I fix it at no charge for 30 days from delivery — no argument, and no debate about whether it technically met the letter of the spec.
Five lines is enough: what it has to do, which systems are involved, and what "done" looks like. You get a fixed price, a delivery date and the questions I need answered, inside 24 hours. If it does not fit, you have lost one email.
Email a briefOr write directly to ai.jidoka.works@gmail.com. "Not for us" is a complete reply.
If you reached this page from an email I sent, this section is the point of it. It exists so you can confirm the sender is a real, identifiable business, and so that stopping the emails takes one word.
| Trading name | AI Jidoka Lab (AI自動化ラボ) |
|---|---|
| Who you are dealing with | Taku — sole operator. This is a one-person business; there is no sales team and nobody else will contact you. |
| What the business does | Contract implementation of workflow automation and API integrations, delivered as white-label overflow capacity for agencies, and directly for small businesses in Japan. |
| Based in | Japan (UTC+9). All work is delivered remotely; there is no UK presence and no on-site work. |
| Contact and complaints | ai.jidoka.works@gmail.com — the same address any email comes from, monitored, and answered by the person who sent it. Complaints go to the same place. |
| To stop receiving email | Reply with the single word "unsubscribe" and I will not contact you again — no confirmation step, no preference centre, no reason required. The address is removed from every future send, permanently. Replying "not for us" has the same effect. |
| How I got your address | From a business contact address published on your own website, recorded with the page it came from and the date it was checked. Emails are addressed to the company, not to any named individual, and I write to UK companies only. |
| No outcome claims | I offer implementation work, not results. I do not promise revenue, leads or savings. See "What I don't promise" above. |
These emails are business-to-business only, sent to companies rather than to individual subscribers, and each one identifies the sender, gives a working reply address and an unsubscribe route. No tracking pixels, no marketing lists, no third-party sharing: your address is used to write to you and for nothing else, and it is not sold, rented or passed on.