This document covers two tracks: (1) A personal Executive Assistant that runs your daily workflow on AI, and (2) A low-hanging-fruit automation pilot across 5 portfolio companies that delivers measurable FTE impact within 90 days.
AI Automation for Macquarie Asset Management
A data center, a regulated utility, a port terminal, and a fiber network appear to have nothing in common. Their commercial models, capital structures, and regulatory environments are completely different. But the back office is not. Finance closes the month the same way. HR onboards the same way. IT provisions access the same way. Procurement raises POs the same way. The variation is at the edges, not the core.
That is why a pilot in 5 carefully chosen companies can produce templates that travel across the rest of the portfolio. The next section explains how we choose which 5.
What It Does For You
| Capability | What it does | Out of the box / Custom |
|---|---|---|
| Morning briefing | Portfolio alerts, pipeline changes, and board prep aggregated across your companies and pushed to you each morning. | Out of the box, tuned to your priorities |
| Meeting intelligence | Pre-meeting briefs pulled from CRM, recent financials, prior notes, and team activity. | Out of the box |
| Action tracking | Follow-ups, commitments, and open items extracted from meetings and email. | Out of the box |
| Portfolio monitoring | Anomaly detection across financial KPIs from your 190 portfolio companies, escalation when metrics drift. | Custom, built against your data sources |
| LP reporting | Automated data aggregation from portfolio companies, draft quarterly reports in minutes instead of weeks. | Custom, built against your reporting templates |
Built on Claude Code. The same system that generated this document is the one Lennart runs his own business on every day. You see exactly what we use, not a sanitized version of it.
How It Plugs In
Day 1 Experience
Concrete picture of what happens when you open the EA on the first day after handover:
| Step | What you do | What you see |
|---|---|---|
| 1 | Open the assistant in the morning | A briefing: overnight portfolio company news, calendar for the day with attached context, open commitments from prior meetings, anything flagged as urgent. |
| 2 | Type: "What changed at Aligned Data Centers this week?" | Structured answer pulling from financial data, news, internal notes, and any prior conversations about that company. Source links included. |
| 3 | Type: "Prep me for the 11am call with the CFO of Southern Water" | Pre-meeting brief: recent financials, last meeting notes, open action items, talking points based on the agenda, questions to ask. |
| 4 | Type: "Draft a follow-up to the Maher Terminals board on the headcount discussion" | Draft email in your tone, with the right tone for that audience, ready to review and send. |
| 5 | End of day: "What did I commit to today?" | List of action items extracted from the day's meetings and emails, with owners and due dates, ready to track. |
What We Need From You
Beyond the 3 hours of meetings, we need access to: (1) your calendar and email (read-only), (2) the systems you use daily that should feed the assistant (CRM, portfolio data, document storage), (3) sample documents that show the tone and format you write in. Setup happens in week 1, takes a few hours from your assistant or IT, and is reversible at any point.
How It Works
Walk through your workflow, tools, and priorities
We build your EA with custom skills and integrations
Live walkthrough, training, and iteration list
Refinements after 2 weeks of daily use
Your Time Commitment
| Activity | Duration | When |
|---|---|---|
| Kickoff session | 60 min | Week 1 |
| Mid-sprint check | 30 min | Week 2 |
| Handover and training | 60 min | Week 3 |
| Follow-up refinements | 30 min | Week 4 |
Security and Data
Claude Code runs locally on your machine. No portfolio data leaves your infrastructure, is shared with third parties, or is used for model training. Full control stays with you.
Per-Company Approach
Two of our consultants interview Finance, HR, IT, Procurement leads. Map top 20 repetitive processes. Score by volume, FTE cost, and automation feasibility.
Build the top 5-8 automations: AI agents, workflow automation, data pipelines. Mostly remote with check-ins every 3-4 days.
Track FTE hours saved, error rates, cycle times. Deliver an impact report with hard numbers, side-by-side with the baseline we measured in week 1.
What the Impact Report Looks Like
A 6-8 page document per company. Process-by-process: hours saved per week, error rate before and after, cycle time before and after, qualitative feedback from the people now using the automation. One consolidated portfolio summary page. Numbers, not narrative.
5 Companies in Parallel
Stagger starts by 1-2 weeks. All 5 complete within 12 weeks. Your time per company: one 30-minute intro call to connect us with the CFO/COO. We handle everything directly with portfolio company management.
Risks and Mitigations
Five things that can derail this kind of program. We have hit each of them on prior engagements and have a working response.
| Risk | Mitigation |
|---|---|
| Portfolio company management resists | Your warm intro to the CFO/COO. We frame the pilot as "free help, free numbers, no commitment." We have not had a portfolio company refuse a free pilot. |
| Data access blocked by IT or security review | Every automation runs on read-only data initially. No writes until reviewed. Most portfolio companies clear this in days, not weeks. We bring our own security documentation. |
| Discovery finds nothing repetitive enough to automate | Has not happened yet. Every back office above 50 FTE has 5-8 obvious targets. If discovery genuinely finds nothing, we drop that company and replace it. You only pay for completed pilots. |
| Pilot results look great in week 12 but adoption decays | Each automation includes a 30-day follow-up after the impact report. We measure actual usage, not theoretical capacity. Adoption issues surface and get fixed before the report is final. |
| Scope creep: portfolio company asks for more during the pilot | Common and a good signal. We capture the requests in a backlog for Phase 2 but do not expand the pilot scope. The pilot has to finish on time to produce credible numbers. |
What We Need From You
Beyond the 5 hours of intro calls, the pilot needs three things from your side: (1) a warm intro per portfolio company (one short email per CEO/CFO is enough), (2) one named sponsor inside your operating team to be our point of contact for status and escalations (roughly 1-2 hours per week), and (3) a willingness to share the resulting impact reports internally so the case for Phase 2 lands with the right people. Everything else we do directly with portfolio company management.
What Happens After 90 Days
You hold the impact report and a clear decision: continue with us into Phase 2, hand the playbook to an internal team, or stop. The pilot is a discrete commitment, not a contract trap. We design it that way intentionally.
The Reporting Problem
CFO reports from portfolio companies typically arrive quarterly with a 4-6 week lag. For an operating partner managing 190 companies, this means most decisions are based on data that is already 2-3 months old by the time it lands. By the time a problem shows up in a quarterly report, it has been a problem for a quarter.
What Real-Time Actually Means
| Today | With AI-Driven Reporting |
|---|---|
| Quarterly PDFs from each company | Live dashboards updated nightly from source systems |
| 4-6 weeks lag from period close | Same-day visibility on the metrics that matter |
| Inconsistent format across 190 companies | Standard templates with side-by-side comparability |
| Anomalies surface after the next board meeting | Anomalies surface in your morning briefing |
| Drill-down requires emails and follow-ups | Drill-down is two clicks from any KPI |
How to Start
This does not require the full 5-company pilot to be in place. It runs as a parallel track:
- Weeks 1-2: Pick 3-5 KPIs that matter most to you (EBITDA trend, leverage, headcount, cash, capex). Map source systems at 5-10 portfolio companies that are already on modern ERP/finance platforms.
- Weeks 3-4: Build the data pipelines. Standardize the format. Stand up the dashboard.
- Week 5+: You start receiving daily data from those companies. Add more companies in waves as systems allow.
Portfolio Archetypes
Infrastructure companies cluster into operational archetypes that predict their back-office patterns. The same invoice processing automation looks different at a data center versus a port terminal. Getting this right up front determines whether pilot results scale or stay local.
| Archetype | Examples | Back-Office Character | Highest-Value Automation |
|---|---|---|---|
| Asset-heavy, low headcount | Data centers, renewables, fiber networks | Small teams, often already digital. Back-office is a high % of total staff. | Financial reporting, vendor management, compliance |
| Asset-heavy, high headcount | Ports, terminals, airports | Large operational workforce. HR/payroll is massive (shifts, safety, training). | HR/payroll, procurement, maintenance scheduling |
| Service/operations-intensive | Waste management, facility services | Distributed operations, many small sites. | Scheduling, invoicing, customer service |
| Regulated utilities | Gas, electricity, water | Heavy regulatory overlay. Unionized workforce in many geographies. | Regulatory reporting, customer billing, asset management |
| Project-based | Infrastructure development, construction | Project finance, contractor management. Fewer recurring processes. | Project accounting, procurement, contractor compliance |
Our Recommendation: Cover 3-4 Archetypes
You will know your portfolio better than this framework, but our recommendation is to spread the 5 across 3-4 archetypes rather than concentrating on one sector. The reason is template reuse: the more variety in the pilot, the broader the rest of the portfolio that the templates work for. A starter shape that has worked elsewhere:
| Slot | Archetype | Purpose | What It Proves |
|---|---|---|---|
| 1 | Asset-heavy, low headcount | Quick win. Small team, modern systems, fast results. | Reporting and vendor management templates that are reusable across many similar companies. |
| 2 | Asset-heavy, high headcount | Largest absolute FTE savings. | HR automation at scale. Templates for ports, terminals, airports. |
| 3 | Service/operations-intensive | Tests distributed operations pattern. | Scheduling and billing automation for distributed sites. |
| 4 | Regulated utility | Tests regulatory constraints early. | What is possible within regulated environments. Avoids surprises at scale. |
| 5 | Largest back-office in your selection | Maximum absolute savings. | The headline ROI figure for the portfolio-wide investment case. |
This is a starting point, not a prescription. We expect to revise it together once we see the actual list of candidates.
Selection Criteria
Within each archetype, score candidates on five dimensions:
| Criterion | What It Means | Why It Matters |
|---|---|---|
| Back-office scale | Total FTE in Finance, HR, IT, Procurement | Drives absolute savings. 1,000 FTE vs. 100 FTE = 10x different impact. |
| Process standardization | Modern ERP/finance systems vs. fragmented legacy | Companies on SAP, Oracle, Workday are dramatically faster to automate. |
| Management alignment | Local CEO/CFO willingness to engage | Cooperative management = 2x faster execution. Resistance kills pilot timelines. |
| Data accessibility | Digital systems with API access vs. paper-based | Determines what can be automated in weeks vs. what needs months of prep. |
| Sector coverage | How many other portfolio companies share this sector | Templates built for one water utility work at another. Sector coverage drives reuse. |
The Selection Process
Plot 190 companies on back-office scale vs. automation readiness. Identify top 20 candidates.
Score top 20 on all 5 criteria. Select 5 covering 3-4 archetypes.
Confirm willingness, data access, no active blockers (restructuring, system migration).
Template Reuse: How 5 Becomes 190
The pilot produces 25-40 automation templates (5-8 per company). Each template is tagged by function, process type, and system requirements. When scaling to additional companies:
- Most automations at a new company are reconfigurations of existing templates rather than ground-up builds
- The remainder require new development for company-specific edge cases
- Each subsequent company is meaningfully cheaper and faster than a pilot company
- The pilot produces the actual reuse rate. The 60-70% range that gets cited in the industry is directional, not yet our verified number for your portfolio.
This is the real answer to scaling. Not linear deployment. Template reuse across archetypes.
Back-Office Process Landscape
A typical portfolio company (5,000 employees) has roughly 400-800 people in back-office functions (Finance, HR, IT, Procurement). That is 8-16% of total headcount. Your target of 20% reduction in these functions means eliminating 80-160 FTE per company.
| Function | Typical Back-Office FTE (illustrative) | High-Automation Processes | Pilot Coverage |
|---|---|---|---|
| Finance | 120-250 | Invoice processing, expense reconciliation, month-end close, variance reporting, intercompany transfers | 2 processes |
| HR | 80-150 | Onboarding workflows, leave management, compliance tracking, headcount reporting | 1-2 processes |
| IT | 100-200 | Ticket triage, access provisioning, asset management, status reporting | 1 process |
| Procurement | 60-120 | PO processing, vendor onboarding, contract extraction, spend analysis | 1 process |
| Reporting | 40-80 | CFO dashboards, board deck prep, KPI aggregation, LP reports | 1 process |
FTE ranges are illustrative based on infrastructure benchmarks for companies in this size range. Actual numbers vary significantly. The pilot replaces these with measured baselines per company. The pilot total per company is 5-8 processes, sequenced to hit the highest-value ones first.
What the Pilot Actually Delivers
The Path from 1-2% to 20%
Reaching 20% requires systematically working through all back-office process clusters across each function. Each cluster follows the same discover-build-measure cycle. Based on pilot results, you can model the full program: how many clusters per company, what team is needed, and what the realistic timeline looks like. The pilot gives you the unit economics to make that decision.
| Phase | Scope | Aspirational Reduction |
|---|---|---|
| Pilot (Months 1-3) | 5-8 processes per company | 1-2% of back-office FTE |
| Phase 2 (Months 4-9) | 10-15 additional processes per company | 5-8% of back-office FTE |
| Phase 3 (Months 10-18) | 25-40 cumulative processes per company | 12-20% of back-office FTE |
Phase 2 and Phase 3 numbers are aspirational ceilings, not commitments. They depend on pilot results, change management capacity at each company, and your appetite for the investment. The pilot replaces these with real unit economics.
What the Pilot Produces
After 5 companies, you have hard data on:
- Cost per automated process (our delivery cost vs. FTE saved)
- Which process clusters yield the highest return across different infrastructure sectors
- Time-to-deploy per automation (sets the pace for scaling)
- Adoption and change management requirements at the portfolio company level
With that data, you can build a credible business case for the full program: total investment, phased timeline, expected FTE reduction per wave, and break-even point.
Scaling Logic
Picking up after the selection and discovery work in Section 6, the scaling sequence is:
- Months 1-3 (Pilot): 5 companies. Prove the model. Establish unit economics. (Detailed in Sections 4 and 6.)
- Month 4 (Playbook): Standardize what worked into a repeatable deployment package. Define the team model for scale (in-house, external, hybrid).
- Months 5+ (Scale): Roll out in waves of 10-20 companies. Each wave reuses templates from prior waves. Your decision on team model is based on pilot data, not on our preference.
Build vs. Buy Decision
You mentioned wanting to start external, then bring it internal. The pilot is designed with this in mind. Every automation we build is documented, transferable, and runs on standard infrastructure. After the pilot, you decide: continue with us, build an internal team using our playbook, or run a hybrid model. The transferability is built into the contract from day one, not promised at the end.
What We Bring
Built on Our Own Architecture
The EA we build for you follows the same architecture we run internally. 72 skills, 7 subagents, integrated with every business system. This document was generated by that system.
Operating Inside Industrial Companies
15+ years inside the operations of manufacturing and industrial businesses. The tooling, the people, the change-management resistance, the politics around back-office costs: infrastructure and manufacturing share more than they differ at this level. We have already worked through the patterns your portfolio companies will throw at us.
AWS Partner
AI applications built on AWS Bedrock. Cloud infrastructure, migration, and managed services capability for production-grade deployments.
Delivery Speed
Small firm, fast decisions. Your EA is live in 2 weeks. First portfolio automations ship within 6 weeks of kickoff.
Why Us vs the Alternatives
You have other choices. Here is the honest version of how we compare:
BLCG / H2W Labs
Operating partner mindset. We use AI inside our own business every day. Small enough to move in days, deep enough to build production systems. Senior people on every engagement.
Big 4 Consulting
Strong frameworks, slow start. 6-12 weeks before code ships. High day rates and pyramid staffing. Often hands off to a junior team after the kickoff slides.
RPA Vendors
UiPath, Automation Anywhere and similar. Strong tools but tool-first thinking. Great for narrow repetitive tasks, weaker for the language and judgment work that AI now handles. License-heavy commercial model.
In-House Build
Eventually the right answer at scale. Hard to start cold without a working playbook. The pilot exists to give you that playbook before you commit to hiring.
The meta-point: this entire document was generated by the system we are proposing. That is the most honest demo we can offer.
Your Core Team for This Engagement
Lennart Hector
Richard Weiher
Heiko Steinbach
Carlos Claure
This is the core team you would work with directly. Lennart owns the relationship. Richard owns the architecture. Heiko runs the multi-company coordination, which is the hardest part of a 5-company parallel pilot. Carlos and a handful of additional senior consultants from our DACH and U.S. teams handle the on-site discovery work. We do not staff junior people on engagements like this.
Selected References
Trojan Technologies
Multi-year engagement spanning training, ERP optimization, and system integration. Multiple expansion deals from a single entry point. Closest match to your utility and infrastructure portfolio profile.
Tsurumi Europe
Multi-country ERP support across DE, UK and FR operations. AI Product Assistant in production. Digitalization roadmap that reduced manual data lookups across the European service organization.
W. Neudorff
16 parallel ERP workstreams, multi-year engagement, ~10 consultants at peak. Full transformation across production, logistics, quality management, and integrations. Our largest engagement to date.
IMA Schelling
Multi-year ERP extensions, system integrations, and ongoing operational optimization. Account upgraded from project work to ongoing transformation partnership.
More Clients We Work With
30+ manufacturing and industrial clients across Germany, Austria, United States, Canada, and Japan.
Recommended: Personal Productivity Deep-Dive
A 60-minute working session where Lennart walks you through his own Executive Assistant live. No slides, no pitch. You see the morning briefing, ask it questions about real companies, watch it draft an email, watch it pull a meeting brief together. By the end you have a concrete answer to "would this work for me." We start here because the EA is the fastest thing to evaluate, the lowest commitment, and the easiest thing to say yes or no to. If yes, we kick off your build the same week.
Alternative: 5-Company Pilot Scoping
A 60-minute call focused on Track 2. Walk through which portfolio companies would be good candidates against the selection framework in Section 6, define the back-office scope, and map out the discovery timeline. Useful if you would rather start with the bigger, slower decision before the personal one.
Combined
Both fit in a single 75-minute call if you prefer to cover everything at once. We can also bring Richard Weiher to that call if you want technical depth on the automation side.
Schedule a CallThe Calendly link reserves a 30-minute holder. If you pick a session length above we will extend the booking on our side once you confirm. Or just reply to the WhatsApp thread with a date that works.
l.hector@blconsultingservice.com