Case Study 02 — Sample Output
Head of AI Operations & Client Services
AI & Automation Consultancy — Remote, Part-time
Strong across all three workstreams. The one real fit question is psychological, not skills-based.
About this output
This is unedited system output from a real job posting evaluation. The evaluation was run on July 11, 2026. The application window closed before a decision was made. This evaluation is documented for portfolio reference.
Phase 1 — Requirements and Fit Assessment
Role Snapshot
The company is a small AI and automation consultancy that helps organisations adopt AI and improve their workflows. This role is 20 hours/week, remote, and splits across three workstreams.
Client services is likely the heaviest: you are the primary contact point for a client portfolio — handling onboarding logistics, scheduling calls, managing follow-ups, preparing meeting notes and action items, and maintaining relationships through regular communication. Operations/coordination runs in parallel: tracking active projects across what appears to be a small internal team, building and maintaining SOPs, documenting processes, supporting new tool rollouts, and helping leadership with planning. AI enablement is the third bucket: researching emerging tools, identifying workflow improvement opportunities for internal and client work, testing and documenting solutions, and helping shape what AI-powered offerings the company brings to market.
This is not a development role. Nothing in the responsibilities column requires hands-on configuration, coding, or deployment. The AI literacy bar is high enough to be credible in client conversations and to spot meaningful opportunities — but execution on the AI side is research, testing, documentation, and handoff.
Where This Posting Aligns
AI literacy and daily use
Direct match — exceeds requirementThe posting lists hands-on Claude, ChatGPT, and Gemini experience as a Nice to Have. All three are in daily use. Five portfolio case studies demonstrate system-level AI work: CS1 (SEO content production system), CS2 (this evaluation), CS3 (Ontario Teacher Unit Planner, full-stack web app), CS4 (file-based RAG architecture across 8+ projects), CS5 (native macOS desktop application). A company selling AI implementation to clients would recognise the gap between someone who has used these tools and someone who has built with them.
Client-facing experience
19 years documented"Act as a primary point of contact," "coordinate client onboarding," "keep client relationships strong," "present meeting summaries and project updates" — every item on this list maps to documented experience. On The Mark Local Marketing ran a consultative client model for nearly two decades: intake, ongoing contact, campaign reporting, addressing concerns, managing expectations.
SOP and documentation
Demonstrated across multiple contextsClient intake SOPs and service fulfilment workflows are documented in the resume database. CS4 (File-Based RAG Architecture) is a knowledge management and documentation infrastructure spanning 8+ projects, built from scratch and maintained across months. The posting's "build and maintain SOPs and documentation" is a direct match.
Process improvement using AI
What the case studies areCS1 reduced a multi-day manual SEO research and writing process to under 30 minutes. CS2 replaced an inconsistent manual job evaluation process with a structured, documented, reproducible system. Both are AI-driven process improvement projects, which is precisely what the AI Enablement column is asking for.
n8n workflow automation
Well past "familiarity"The posting lists "familiarity with workflow automation platforms" as a Nice to Have. 14 active n8n workflows with webhook endpoints, conditional branching, multi-step orchestration, API-connected integrations, and direct MCP integration via n8n-mcp are documented and specific.
Working independently with minimal supervision
19 years self-employedNo ambiguity here.
Managing multiple priorities and deadlines
Multi-client consultancy experienceRunning SEO, PPC, content, and client management simultaneously across multiple accounts is documented. This matches the "coordinate multiple projects and priorities at once" requirement directly.
Agency and consulting background
Meets Nice to Have fully"Background in consulting, technology, or agency work" is listed as a Nice to Have. All three apply.
Where This Posting Diverges
CRM experience
Soft divergence"Experience with CRM systems and business software" is listed as a Nice to Have. Documented experience is light pipeline tracking in Monday.com and Trello at a basic level — not substantive CRM platform experience. A client services role will almost certainly have a CRM in daily use (HubSpot, Salesforce, or a vertical-specific tool). There's a learning curve here. It's not a disqualifier — the posting doesn't require CRM expertise — but it's a genuine gap to name honestly.
Client relationship management as a primary daily activity
Soft divergenceThis is the only meaningful concern, and it's psychological rather than skills-based. The capability is not in question: client relationship maintenance has been the job for 19 years. The profile documents that sustained client-facing exposure — regular check-ins, reactive availability, ongoing relationship management — is a drain. At 20 hours/week, if client services accounts for half the time, that's roughly 2 hours of active client contact per day. At that volume it's likely manageable. At 40 hours/week it would be a different calculation. The part-time format is a real mitigating factor.
"Head of" title ambiguity
Soft divergenceThe title implies seniority. The responsibilities read closer to a Client Success Manager or AI Operations Coordinator. In a small, growing company, "Head of" at this scope typically means you're the only person in that function. That's not a gap — it's a title management consideration. Salary expectations should be calibrated to the actual scope, not the title.
No hard divergences. Nothing in this posting would filter you out at a skills level.
Candidate Tier Assessment
AI literacy
Posting bar is proficient daily use. Building production systems exceeds it.
Client-facing experience
19 documented years of exactly what the posting describes.
Documentation and SOPs
CS4 and consulting SOP work both directly relevant.
Workflow automation
14 active n8n workflows with MCP integration is well past "familiarity."
CRM experience
Only basic pipeline tracking documented.
Overall
Strong BETTER candidate with BEST-tier credentials on the two dimensions this role cares most about — AI literacy and client-facing experience. The CRM gap is real but soft. The role does not require it as a primary qualification.
Phase 2 — Psychological and Environment Fit
Day-to-Day Fit Check
The responsibilities section lists client services first and most prominently, which typically signals where the time allocation goes. Walking through what a typical day likely looks like and checking it against documented energy patterns:
Written follow-ups, meeting summaries, action item tracking. Asynchronous, written, deliverable-based. Clear finish line — a meeting summary is done when it's accurate and complete. No ambiguity about whether you did it right. Positive fit.
Scheduled calls and onboarding sessions. Structured and predictable by nature. Preparation follows a repeatable format. This lands closer to "predictable routines" than to "real-time public performance." Manageable.
"Keep client relationships strong through regular communication." This is where the fit question lives. If this means structured written updates and scheduled check-ins, it maps well. If it means reactive availability — clients calling unexpectedly, open-ended relationship maintenance with no defined deliverable — it pulls toward draining territory. The posting doesn't specify which. This is worth probing in an interview.
AI enablement: research emerging tools, identify opportunities, test and document. Exploratory ambiguity — no "correct" answer expected, the task is discovery and tinkering, with findings shared through documentation. Paid to figure out what AI tools can do is a documented draw, not a drain. If the role weighted more heavily here, the fit score would be higher.
Operations/coordination: track deliverables, maintain SOPs, support tool rollouts. Structured, deliverable-based, concrete finish lines. Strong fit.
Net day-to-day assessment: At 20 hours/week (roughly 4 hours/day), this is a sustainable role even if client services is the largest time bucket. The part-time format is a real mitigating factor. At this volume, the draining elements are bounded. The energising elements (AI research, documentation, structured coordination) are present and genuine.
Environment and Authority Red Flag Screen
Volatile or unpredictable management
Soft flag"Close working relationship with leadership" is listed as a benefit. In a small, growing AI consultancy, this almost certainly means reporting to a founder or CEO. That dynamic can go either way: it can be the right-hand-man relationship that suits the profile at its best, or it can introduce volatility if the founder operates without clear expectations and regular feedback. The posting's framing is positive and measured, not red-flag language — but the absence of detail means you don't know yet which version you're walking into. Ask directly in the interview about how communication and feedback work.
High real-time social exposure as primary activity
Soft flagThe client services column raises this question, but the part-time and "flexible hours" framing materially limits the exposure window. A primary point of contact role at 20 flexible hours/week is not the same as a full-time client-facing account manager role. Soft flag, not hard.
Chronic urgency culture
ClearNot signaled. No "startup pace," no "must thrive under pressure," no "constantly shifting priorities." The 90-day success criteria are specific and sequential, which suggests an organisation that thinks in structured milestones.
Arbitrary or public feedback structures
ClearNot signaled. No evidence of public evaluation, arbitrary review processes, or undefined performance criteria in the posting language.
Politically complex hierarchical environments
ClearSmall company, direct leadership relationship. No signals of complex internal politics or multi-layer approval chains.
Ambiguous deliverables with no finish line
Soft flag"Spot process improvement opportunities" and "help shape AI-powered client offerings" are open-ended. But the 90-day success criteria name concrete markers: "become a trusted point of contact for client communication," "coordinate active projects and follow-ups smoothly," "identify where AI can improve efficiency." Those are close to performance ambiguity — success is somewhat subjectively defined — but specific enough to work against. Soft flag, worth clarifying in interview.
Scope creep phrasing
Clear"And other duties as assigned" does not appear. The three-column structure (client services, operations, AI enablement) is clearly bounded.
Final decision-maker or primary public-facing authority
Positive matchThe role is explicitly positioned as a coordination function working closely with leadership, not as an independent authority. You are the right hand, not the face of the company. This is the right-hand-man identity in job-posting form. Positive identity match.
Zero hard red flags. Two soft flags worth probing in an interview: the direct leadership relationship (clarify how feedback and communication work) and the client services column's reactive availability question (clarify whether this is a structured cadence or open-ended availability).
Vagueness Assessment
The posting is relatively clear for its type. The three-column structure is logical and internally consistent. The 90-day success criteria are specific enough to evaluate against.
Missing information worth noting:
- —No salary range. "Competitive salary" with no number for a part-time role. For 20 hours/week, you need to know what that means before investing in a full application. Worth investigating — check LinkedIn salary data or ask during a screening call.
- —No client base described. Who are their clients? What industries? What size? Managing three enterprise clients is a different job than managing twenty SMBs.
- —No team size. Implied small by "as we grow" language. But "small" could mean two people or ten.
- —No reporting structure details. "Close working relationship with leadership" doesn't name a manager or describe the reporting relationship concretely.
None of these are red flags on their own — this is a normal level of detail for a mid-level posting. But the missing salary range and client context are both things to resolve before writing a polished application.
The Honest Verdict
Apply. This is a legitimate fit.
The role's primary technical requirement — AI literacy — is the area where you have the widest advantage over a typical applicant. The company sells AI and automation implementations to clients. Someone who has built five AI portfolio pieces independently, runs 14 n8n workflows, uses Claude at API level, and has a documented methodology for AI-driven process improvement is a meaningfully different candidate than someone who uses ChatGPT at a competent level. That gap is real and it matters to a company whose entire value proposition is AI delivery.
The client-facing concern is real but bounded. 19 years of documented client work. The part-time format limits the drain to a sustainable volume. The right-hand-man positioning is explicitly present in the role description. The absence of hard red flags is also signal — this posting doesn't contain the volatility or urgency language that characterises the roles that would grind you down.
Lead angle:AI enablement depth. Don't open with the SEO background — it doesn't connect to what this company does and risks undercutting the AI positioning. Open with the fact that you've been building AI systems for your own work and your clients' work, ground it with one concrete example (CS1's before/after is the cleanest, fastest proof), then layer in the 19 years of client consulting as the second credential that makes the AI work deployable in a client-facing context.
Framing risk:The case studies are the differentiator, but they need a quick translation for someone at a small consultancy reading a coordinator-level application. The frame isn't "I built five complex systems." The frame is "I've been doing the work your clients are trying to do — using AI to fix broken processes, document systems, and make workflows repeatable. I've done it for myself. I know what the problems look like from inside."
One Thing to Do Before Applying
Research the company specifically before writing the application. The posting is light on client industry and RPA specifics. Understanding whether they work in healthcare, professional services, operations, or another vertical would let you name a relevant case study angle in the cover letter rather than using a generic AI implementation framing. A company whose clients are healthcare organisations is a different application than one whose clients are accounting firms. Ten minutes on their LinkedIn, website, and any public client mentions would sharpen the positioning considerably.
What comes next
When the verdict is Apply, the system moves to application writing. A resume and cover letter are generated against the full skills and experience database — every documented role, credential, and accomplishment — cross-referenced with the specific job posting. Findings from Phase 1 and Phase 2 inform the framing directly: the alignment section shapes what gets foregrounded, the divergence section shapes what gets addressed or reframed, and the lead angle from the verdict shapes the cover letter opening.
The documents then go through a two-phase editor agent before human review. Phase 1 runs blind — no job posting — and checks the writing against a named list of AI tells: banned words, em dash usage, zero-contraction prose, metronomic sentence rhythm, negative parallelism, trailing significance claims, and specificity density. Phase 2 layers in the posting and checks for missing keywords, buried relevance, and tone mismatch against the role's language. Output is a prioritised edit list returned to the main agent for implementation before the documents are finalised.
This evaluation was run through the CS2 system on a real job posting. The application window closed before a submission was made. This output is documented here as a portfolio reference for Case Study 2.