Portfolio / 2026 · US and UK hours

Give me a loose brief.I'll hand backorganized, checked work.

Hi, I'm Eddah Dena. I'm based in Nairobi, work across US and UK time zones, and focus on operational analytics and executive support.

For over a decade, I've analyzed audit data to spot red flags, and today I manage the internal data and CRMs that help audit leadership track clients, teams, and workflows. I'm now bringing that rigor to operations teams and the executives who lead them: learning your systems, spotting friction, and bringing clear, data-backed recommendations for your approval.

See sample tasksHow I got here

Now · Built this portfolio to show my sample tasks

Eddah Dena, wearing glasses and a denim shirt, at a conference.
Eddah Dena · Nairobi (EAT, UTC+3)

01About

How I got here

For over a decade, I've worked with audit teams to analyze audit data and identify red flags, turning large, messy datasets into findings people could act on.

Today, I also manage internal data and CRMs that help audit directors and leadership keep track of their clients, their teams, and workflow expectations. That work sits where analysis meets operations, and it's the bridge I'm building on as I move into operational analytics and executive support.

My approach is context-first. Well-run teams don't need someone to tear down their systems. I start by understanding why things are done a certain way, then use the judgment I built in audit to suggest where they could run better.

  • Rapid Integration: I already work daily in Excel, Power BI, SharePoint, and Notion, and I'm building hands-on experience with HubSpot, Monday.com, and Make. I adapt to your tools and your team's communication style rather than asking you to adopt mine.
  • Calibrated Recommendations: Audit taught me to back every finding with evidence. When I spot friction or waste, I analyze it, propose a solution, and bring it to you for approval before anything changes. You make the call; I follow through.
  • Uncompromising Quality: I run every deliverable through a strict, 12-point pre-send QA checklist. You can trust that what I hand over is verified, accurate, and ready for immediate use.
  • Proof of Work: Because my day-to-day work is confidential, I've built realistic sample tasks with synthetic data to show how I would handle operations and executive-support work: how I structure it, apply judgment, and verify the output. Explore them at nrold.com.

Feel free to check out my Build Log to see what I'm learning along the way!

  1. 0110+ years

    Making sense of financial data

    What makes a report something people trust?

    Clear, checked numbers are what let people decide with confidence. Everything else is decoration.

  2. 022026

    Choosing remote support work

    Where else do those skills matter?

    Executives and operations teams need what I've always done: messy inputs turned into organized, checked work.

  3. 03Sep 2026

    Practicing on simulations

    How do I show my work when my day-to-day work is confidential?

    I practice on realistic, fictional briefs with synthetic data, so I can show every file without exposing anyone's information.

    The first one: a CEO's week

  4. 04Oct 2026

    Turning mistakes into a checklist

    Why do small errors still reach the first review?

    Six errors in my first three samples became 12 checks I now run before anything is sent.

    The pre-send checklist

  5. 05Now

    Next up

    What do remote teams need from me next?

    Building out advanced operations and analysis samples using the tools modern remote teams rely on: HubSpot, Monday.com, and Make.

02Work

Sample tasks

Every task is a work sample: a fictional scenario with synthetic data, not client work.

03Process

How I work

  1. Clarify the goal

    I ask targeted questions to define the objective, deadline, and what "done" looks like. I'm highly async-friendly, so I document everything upfront to save us from unnecessary calls.

  2. Structure the mess

    I take your loose brief or zero-draft and break it into actionable steps. I set up simple tracking and flag missing info early so the project never stalls.

  3. Execute and verify

    I do the deep work, then run it through a strict personal QA checklist. I don't hand over anything I haven't double-checked, so it arrives polished and ready to use.

  4. Deliver and refine

    I present the final output with clear notes on any decisions you need to make. I track lessons learned in my Build Log, ensuring transparent, continuous improvement.

04Tools

Tool stack

Each status is honest: "Used" means a sample task on this site relies on it.

Coordination

Operations

  • SharePointUsed daily
  • CanvaUsed daily
  • n8nPracticing

    Social posting and task-move alerts by email and SMS

  • Power AutomatePracticing

    Daily Excel file backup

  • Google FormsPracticing
  • Monday.comStarted
  • HubSpotStarted
  • MakeStarted
  • ZapierStarted

Analysis

AI

05AI

How I use AI

Claude
Working faster on everyday tasks, with me directing and checking the work. It also created the practice scenarios behind the sample tasks on this site.
Perplexity
Research.
ChatGPT
Quick rewrites, tone changes, turning notes into action lists, brainstorming and image generation.
NotebookLM
Studying.
Leonardo.ai
Image generation.
I treat AI as an efficient apprentice. It makes first drafts from my instructions, speeds up routine work, and helps me brainstorm and work through complex tasks. I review every draft thoroughly and oversee every output to protect integrity, accuracy, and privacy.

Each sample task says exactly what AI did and what I checked.

06Log

Build log

Dated notes on what I built, learned, broke and fixed.

  1. Built

    Built this portfolio to show my sample tasks

    I built this site to show my practice work as finished samples, each with the brief, my approach, the files and what I’d do differently. Every sample is a fictional scenario built on synthetic data, so nothing private goes online. The site refuses to publish if any placeholder text is left in, which is my pre-send checklist applied to the site itself. Next, I’ll finish the draft tasks for operations and analysis.

  2. Learned

    Learned travel and calendar management

    I practiced calendar and travel management on two scenarios: a CEO’s week rebuilt after nine conflicting requests, and a two-stop business trip planned within a $1,600 budget. Both taught me the same thing: write down the person’s rules first, then judge every option against them. That is how 18 calendar clashes became 14 documented decisions, and how the trip came in at $1,466 with a fallback plan ready. Next, I’ll run my pre-send checklist before the first review, not after it.

    Related sample task

All log entries

07Contact

Get in touch

Have a messy brief, a chaotic calendar, or data that needs making sense of? Let's talk. I'm currently open to new opportunities and respond to emails within 24 hours.

Email me