Operations infrastructure for small nonprofits.
I build the systems that keep a 5-to-15-person organization running — finance workflows, IT administration, intake processes, and the documentation that holds it all together. Built so they still work after I leave.
What I do
- Finance operations
- Accounts payable and receivable workflows, Bill.com and QuickBooks administration, grant expenditure tracking, and clean documentation packets for your bookkeeper.
- IT without an IT department
- Microsoft 365 administration, device setup and inventory, security baselines, and nonprofit licensing that stops overpaying. TechSoup is usually the first thousand dollars I save.
- Systems that survive turnover
- Intake systems, SOPs, policy libraries, and handoff documentation written for the person who holds the role next — not for the consultant who built them.
- Interim operations coverage
- Leave coverage and vacancy bridging at a leadership level, with a complete handoff package as the standing deliverable from day one.
- Data cleanup and reporting
- CRM hygiene, donation coding, dashboards your board can read, and the operational metrics that make Monday mornings shorter.
How engagements work
Three shapes cover most of what organizations need. Every engagement, whatever its shape, ends with documentation your team owns.
| Shape | What it looks like | Typical length |
|---|---|---|
| Fix one thing | A single broken or missing system — an intake process, a device rollout, a finance workflow — scoped, built, documented, and handed over. Fixed scope, defined deliverable. | 2–4 weeks |
| Interim coverage | Full operations coverage during a leave or vacancy, run at a leadership level, with the handoff package built as I go rather than at the end. Weekly hours, monthly invoicing. | 2–4 months |
| Standing support | A few hours a week keeping systems maintained, questions answered, and documentation current after a build or a coverage engagement ends. Light retainer, cancel anytime. | Ongoing |
About
I'm Ewan Andreasen, an operations consultant in Seattle. My background runs through data work, housing and homelessness services, and behavioral health — the kinds of organizations where the mission is urgent and the operations budget is one person's spare afternoons.
I've administered the full small-nonprofit stack — Microsoft 365, SharePoint, Bill.com, QuickBooks, Asana, EveryAction, 1Password — and my working principle is simple: if a system only works while I'm in the room, it isn't finished.
Common questions
We've never hired a consultant. How does this start?
With a conversation and a short list. I look at what's breaking, what's undocumented, and what's costing you money, and give you a prioritized list — whether or not we work together. If we do, we pick the top of the list and scope it as a fixed engagement.
What does this cost?
I bill hourly, invoiced monthly with net-15 terms. Fixed-scope engagements get an hours estimate up front, and I flag it early if reality diverges. Nonprofit budgets are real constraints and I scope to them.
Do we need to be a nonprofit?
No — small teams anywhere have the same operations problems. Nonprofits are where I have the deepest pattern knowledge, including the vendor discounts and licensing programs most small orgs don't know they qualify for.
What happens when the engagement ends?
You keep everything: documentation, credentials transferred properly, systems in your tenant and accounts, and a handoff package written for whoever runs operations next. My own access gets revoked on a checklist. That's the point.
Get in touch
Currently engaged through November 2026; booking January 2027 starts.
The first conversation is free and useful either way — you'll leave with a prioritized list even if we never work together. Write with a couple of sentences about your organization and what's not working. I reply within two business days.
Email: ewan@ewanandreasen.com