Every Question a Hiring CEO Asks — Answered Straight

Abraham Otieno is a Nairobi, Kenya-based Executive Assistant, Chief of Staff, and Operations Partner supporting founders, CEOs, and leadership teams remotely worldwide. Past clients include MSTRpay (Sweden), Pioneer Outsourcing BPO, M-KOPA, OKash Kenya, Generation Kenya, Insight BPO, and Dial Africa.

An executive assistant owns the executive's day — calendar, inbox, travel, meeting prep, follow-through. A chief of staff owns the company's execution rhythm — leadership cadence, OKRs, board operations, cross-functional initiatives. At 15–80 person companies, most founders need a hybrid of both, which is how most of my engagements run.

A chief of staff works through the CEO on strategy execution: cadence, decisions, initiatives. An operations manager works in the systems: SLA tracking, dashboards, onboarding, process documentation. The chief of staff makes the leadership team effective; the ops manager makes the delivery team reliable.

Part-time and senior: typically 10–25 hours a week of focused, experienced operating capacity instead of a full-time hire. You get the discipline and judgment of a senior operator without the $200K+ fully-loaded salary, on monthly terms you can scale or stop.

Three structural reasons: the EAT time zone (UTC+3) overlaps Europe fully and the US East Coast meaningfully in one working day; Nairobi has a deep pool of internationally-trained, English-fluent senior operators; and the cost is 50–70% below US/UK equivalents at the same seniority — without the quality compromise of typical offshore hires.

An individual senior operator. No handoffs to juniors, no account managers, no templates. The person on the discovery call is the person doing the work — and the person whose name is on three published testimonials.

Core hours 08:00–18:00 EAT (UTC+3), flexed by agreement: that's full live coverage of European business hours and US East mornings to ~early afternoon. US West Coast runs async-first with shifted check-ins. Urgent-response rules are agreed in the engagement doc.

Discovery call within 48 hours of booking. Proposal within 24 hours of the call. Signed and kicked off within five business days. Most clients see their first deliverable in week one.

Three formats — hourly retainer (ongoing EA support), monthly retainer (chief-of-staff or operations scope), or fixed project pricing (system builds, market entry, launches). Exact rates depend on scope and seniority of decisions handled, agreed in the discovery call. No setup fees, no long minimums.

Based on past engagements: 15+ hours per week back on your calendar by week four, a working operating cadence (decision log, tracker, weekly report) by week two, and measurable team-response improvement within a quarter — the SLA-discipline system behind the 80% response-time improvement takes about that long to compound.

Mutual NDA before any sensitive detail is shared. Client-owned drives and systems, encrypted storage, 2FA enforced, no personal channels for client work, and written data-retention rules at engagement end. I work within your security policy if you have one.

Where it makes the work faster and you approve it — drafting, summarising, research. Never for confidential data without your explicit sign-off on the tooling, and never as a substitute for judgment. The decision-rights doc covers AI usage explicitly if you want it to.

Cash engagements as standard. For longer fractional chief-of-staff engagements with early-stage companies, a cash-plus-small-equity structure is discussable — raise it on the discovery call.

Your stack, not mine: Google Workspace, Microsoft 365, Slack, Notion, Asana, ClickUp, Monday, HubSpot, Salesforce, Calendly, Loom, Zoom, and lightweight Sheets/Excel dashboards where a full CRM is overkill.

Everything is built in your systems and documented for handoff — SOPs, playbooks, decision logs, dashboards. The explicit design goal is that the systems survive me, whether you hire a full-time replacement or your team runs them.

Yes — common pattern: I design the systems (CRM, SLA tracker, decision log, cadence) and train your in-house team to run them, then step back to oversight or out entirely. I'll recommend whichever structure moves the needle fastest, including the one that pays me less.

No — BPOs, fintechs, NGOs, and founder-led companies from 5 to several hundred people. The common factor isn't stage; it's a leader whose week is leaking and a team whose execution depends too much on heroics.

Heaviest in week one (kickoff plus systems access, roughly 2–3 hours total). After that: one weekly 20–30 minute check-in and async approvals. If you're spending more time managing me than that, something is mis-scoped — and fixing it is on me.

Check the named testimonials and companies on this site, the published case studies and live portfolio artifacts, my LinkedIn and Upwork profiles, and ask for direct references on the discovery call — happily provided. NDA comes before any confidential detail moves.