1
First conversation
We meet — in person if you're in Pittsburgh, otherwise a call — and talk about your situation. I'll tell you honestly whether I can help, and if so, what I'd recommend. This is always free.
How I Work
Is this a good fit?
I'd rather be honest about fit than waste your time. Here's how to tell whether we're right for each other.
Won't work Will work
Won't work
You need a full team.
I sometimes pair up with other consultants or contractors, but I can't provide enterprise-scale capacity.
Will work
You need the right person, not a department.
I work as a stopgap for organizations that don't have the budget for a full-time engineer, and as an ongoing technical partner for ones that want to keep things lean. Either way, you get someone who knows your systems.
Won't work
You want to deposit instructions and receive output.
I don't work that way, and I don't think it produces good results. The best outcomes come from regular conversations, shared context, and honest feedback in both directions.
Will work
You want to think through problems together.
We meet regularly, talk through what's working and what isn't, and adjust direction together.
Won't work
You want to patch a system that should be replaced.
I'll adapt within existing systems when it makes sense, but I won't deepen the technical debt of something fundamentally broken. If a system needs to be replaced rather than band-aided, I'll tell you that directly.
Will work
You want work that's bus-proof.
Everything I build is documented and designed so that someone else can pick it up. If I get hit by a bus tomorrow, your systems keep running and the next person can understand what I've done.
If I'm not the right fit, I'll tell you — and I'll refer you to someone in my network who is.
The Process
How an engagement works
Start with a conversation, prove it on something small, then grow from there.
2
Start small
I'll encourage you to begin with a small project with clear goals. You get something useful quickly, and you get a feel for how I work before committing to something larger. If the fit isn't right, you'll know early.
3
Working together
We touch base every one to two weeks, in person when possible. Between check-ins, I send short progress updates at least once a week so you always know where things stand. I keep you informed on technical decisions and encourage you to ask about anything you don't understand. Your systems should never be a mystery to you.
4
Growing from there
Once the first milestone is done, we decide together what comes next — additional features, a new project, or an ongoing retainer. And if you want to bring work in-house, I'll help you hire the right person and hand everything off cleanly.
Pricing
Most paid engagements start at $2,000. Every engagement starts with a free conversation. After that, I'll recommend a pricing model and quote you a specific number before any work begins. What I quote is what you pay.
Project / Milestone
You know what you need built.
We agree on the scope, I quote you a fixed price, and you pay when milestones are hit. Ideal for work where you need a clear number for the budget, especially grant-funded work.
Retainer
You need an ongoing technical partner.
Predictable monthly cost for dedicated hours. Retainers scale from a few hours of advisory time to deeper ongoing work. Per-hour cost decreases with volume. Best if you want a long-term relationship with guaranteed availability.
Hourly
You need a few hours of help.
Straightforward, no commitment. Per-hour rate is higher than retainer or project pricing. Best for small or one-off requests.
Pro bono work
If you can't pay, I also set aside ten hours every week for pro bono work.
Read more about how it works and whether your organization qualifies →Sound like a fit?
The first conversation is always free. Let's talk about your situation.