I turn requirements from non-technical clients into scoped tasks, timelines, and documentation, then keep the work moving until it ships. I have delivered healthcare and insurance software, led client teams, and allocated a $2.6M budget. Computer Science graduate, Iowa State, May 2026.
Case Studies
The problem, the team, the risks, the calls I made, and the measurable result.
Pippa: A two-sided healthcare platform shaped by conversations with 200+ clinics. I owned scope, task breakdown, the release calendar, and the documentation clinics onboard with.
W.R. Berkley: Underwriters were retyping the same record between systems. I mapped the manual path, scoped the replacement, and coordinated the release across three teams.
Iowa State: A $2.6M+ annual budget, competing requests, and stakeholders who did not work in software. Every allocation had a written decision.
HerdRight: Five people, three workstreams, one marketplace. I kept payments, listings, and pricing on track and kept the team from building side projects.
VerifyAI: One day, four people, one job. I scoped the work down to what had to run, and we took 1st of 28 teams.
Neighborhood Finance: A nonprofit needed to know whether an address qualifies for a loan program. I led a team of four and left the client able to maintain the tool without us.
How I Run a Project
Requirements & Discovery: Shadow the people doing the work and write down what they repeat. 229+ clinician calls at Pippa, underwriters at Berkley.
Scope & Task Breakdown: A prioritized backlog, a written definition of done, and a recorded no for everything that waits.
Timelines & Releases: Release plans from first requirement through launch, with review and approval steps every team can see.
Cross-Team Coordination: Schedules and handoffs aligned across engineering, QA, DevOps, and the business stakeholders.
Budget Tracking: Requests evaluated against funds actually available, with every allocation documented.
Status & Risk Reporting: Short written status that turns technical detail into next steps, and flags risks before they become slips.
Key Metrics
Pippa: Ran discovery with 200+ clinics and delivered a two-sided healthcare platform with 10K+ daily users, owning scope and release timelines.
W.R. Berkley: Saved 4,500+ hours a year by mapping and automating manual data entry, coordinated across three teams.
Student Government: Reviewed and allocated $2.6M+ in annual funding, with a written record for every decision.
Neighborhood Finance: Delivered a mapping system saving the client $100,000+ a year, plus the documentation they maintain it with.
HerdRight: Coordinated payments, listings, and pricing for a marketplace that reached 30K+ users and was acquired.
VerifyAI: Scoped and shipped a working product under a one-day deadline and took 1st of 28 teams.
FAQ
How do you gather requirements?: Discovery calls and shadowing. I write down the jobs people repeat, then turn those into scoped, tracked work. At Berkley that is how we found 84+ hours a week of manual rekeying.
How do you handle scope creep?: A written definition of done and a recorded reason for every request that waits. Fixed deadlines get a smaller product, not a vaguer one.
How do you keep stakeholders aligned?: One prioritized backlog, short written status reports, and review and approval steps that every team can see before a release.
How do you manage risk?: I name the risk early, assign an owner, and decide the response in writing. Each case study on this site lists the main risks and what I did about them.
Does your technical background help?: Yes. I can read the code, the data model, and the pipeline, so I scope work engineers agree with and spot schedule risks early.
What role are you looking for?: Project management roles where I can own delivery alongside an experienced team. I am based in Chicago.