DA9: Running automation for a business
Growing as an automation specialist
🎯You'll be able to
Plan your next steps as an automation specialist: roles, portfolio, pricing approach and staying current.
🏠The everyday picture
An apprentice electrician first wires single rooms, then whole houses, then designs the wiring of a building with a team. The craft is the same; the scale and responsibility grow.
📘What it really is
- Common roles along this path:
- Automation specialist / integration developer: builds and maintains workflows for one business or many clients;
- RevOps specialist: owns the revenue process, CRM and reporting across marketing, sales and service (DA8);
- Enterprise automation architect: designs automation for large organisations: standards, platforms, security reviews and governance across many teams.
- What grows with each step:
- scale: from one workflow to hundreds;
- governance: naming rules, review before launch, shared credentials policy, a catalogue;
- platforms: larger organisations may use enterprise tools (for example, integration platforms and robotic process automation) alongside n8n or Zapier;
-
communication: explaining trade-offs to managers and leaders.
-
A portfolio shows capability better than a list of tools: write short case studies with the problem, the design, the result in numbers and what you'd do differently. Remove client names and personal data unless you have permission.
-
Keep learning from the next paths: Backend (building APIs), Data (analytics), AI/ML (AI steps in workflows) and Cybersecurity (protecting integrations).
📝A worked example
A portfolio case study, written from this path's projects:
Payment to accounts automation for a textile retailer. Problem: invoices were created by hand up to 3 days after payment, and about 20 payments a month couldn't be matched. Design: signed payment webhook, duplicate check, API confirmation, invoice and CRM update, alerts with a runbook. Result: invoices within 5 minutes; unmatched payments down to about 2 a month; no duplicate invoices in 3 months. Next time: include refunds in the first phase.
🌍Where it's used
- Job applications for automation and RevOps roles.
- Freelance proposals, where clients want to see similar work.
- Promotions, where results in numbers make the case.
📝Case scenario
Two candidates apply for a RevOps role. One lists "n8n, Zapier, HubSpot, APIs". The other shows three short case studies with before-and-after numbers and a runbook sample. The second is invited to interview, because the hiring manager can see the work.
🖱️Try it
Write one portfolio case study from your Sharma Textiles work, using the structure above: problem, design, result in numbers, and what you'd do differently.
⚠️Common mistakes
- A portfolio of screenshots. Sign: no proof anything works. Fix: show the tests, the failure handling and the handover pack.
- Claiming results you didn't measure. Sign: "saved 40 hours a week" with no source. Fix: report what you tested and label estimates as estimates.
🛠️For your project
The three projects and capstone are your portfolio. Your self-check evidence links (repository, test output, demo) are what you would show an employer or client.
✅Quick check
What does an enterprise automation architect focus on that a single-workflow builder may not?
Show the answer
Standards, governance, platform choices and security across many teams and workflows.
What makes a strong portfolio case study?
Show the answer
A clear problem, the design, results in numbers, and an honest note on what you'd change.