Assess
We need clarity.
Understand what’s happening, what matters most, and where to focus first.
Explore assessmentsIndependent Technology Guidance for Nonprofits
Technology problems rarely arrive neatly labeled.
You may know something isn’t working, have a major decision coming up, need help getting a project over the finish line, or simply need someone experienced to take more ownership of technology.
I help nonprofits understand what’s really happening, decide what makes sense, and make practical progress.
No obligation. No sales pitch. Just clarity.
Start where you are
You don’t need to arrive with the solution. That’s part of what I help you determine.
Start with what’s happening in the organization. I’ll help translate the business or operational problem into the underlying technology, process, ownership, or capacity issues and determine what kind of response makes sense.
Advise
We need experienced guidance.
Pressure-test a decision, build a plan, or work through a difficult technology question.
Explore advisoryImplement
We need help getting it done.
Add experienced technical capacity to configure, fix, improve, or move a project forward.
Explore hands-on supportLead
We need someone to take ownership.
Add ongoing technology leadership to own priorities, vendors, projects, and follow-through.
Explore fractional leadershipTechnology Problems Don’t Always Look Like Technology Problems
The visible problem may only be the symptom.
Technology issues often show up first as operational friction, confusing decisions, recurring workarounds, or too much responsibility landing on the wrong people.
It looks like...
- Disconnected systems and duplicate work
- Manual workarounds everyone has learned to live with
- Reporting that takes too long or is hard to trust
- Projects that keep drifting or restarting
- Vendors holding critical knowledge
- Technology spending that is hard to explain
It sounds like...
“Why is this so complicated?”
“Nobody really owns this.”
“We keep fixing things, but the problems come back.”
“I know we need help. I’m just not sure what kind.”
It feels like...
Technology is taking more time and attention than it should, decisions are harder than they need to be, and staff are compensating for systems instead of being supported by them. Over time, that unnecessary friction can contribute to overload, burnout, and turnover.
Leadership + Strategy + Operations + Technology
Technology problems cross organizational lines.
The issue may start with a system, a decision, a workflow, a vendor, or a gap in ownership. I work across those boundaries because solving only one piece often leaves the real problem in place.
Leadership
Set direction, establish priorities, create ownership, and keep technology connected to organizational needs.
Strategy
Work through difficult decisions, build roadmaps, evaluate options, and plan investments.
Operations
Improve workflows, coordinate vendors, clarify responsibilities, and strengthen follow-through.
Technology
Configure systems, clean up implementations, troubleshoot problems, integrate platforms, and get projects working.
How I work
As much or as little ownership as you need.
I can help with a specific decision, work alongside your team, take on hands-on technical work, or step into a broader leadership role. The level of involvement depends on what will be most useful.
Lead
Take ownership of priorities, decisions, coordination, and follow-through.
Support
Help your team think through decisions, build plans, and move work forward.
Do
Work directly in systems, configurations, implementations, and technical projects.
Technology Effectiveness Assessments
Not sure where to focus? An assessment can create the map.
When the problems are connected or the right starting point is not obvious, an assessment provides a structured look at what is happening, what matters most, and what to do next.
Depending on the situation, that may include systems, data, workflows, governance, security, vendors, staff capacity, adoption, cost, and technology ownership.
An assessment is one starting point, not a required first step.
What you get
A clearer picture
Understand what is actually happening across technology, operations, people, and providers.
Priorities
Separate the important risks and opportunities from the things that can wait.
Practical recommendations
Identify realistic actions based on your organization, capacity, constraints, and goals.
A path forward
Know what to address now, what to plan for later, and what may not need attention at all.
The next step might be advisory support, hands-on improvements, fractional leadership, another provider, or work your own team can handle internally.
Make progress without creating tomorrow’s problem
The immediate solution matters. So does what happens after it is implemented.
A solution can work technically and still create problems later if nobody owns it, staff do not have the capacity to support it, costs keep growing, or it adds more work than it removes.
Good technology decisions account for what happens after the project is finished, not just whether it can be done.
Questions worth asking
01
Who will own this?
02
What will it cost to operate and support?
03
How does it fit with the systems you already have?
04
Is it secure and sustainable?
05
Can staff realistically manage it with the time and capacity they have?
06
Is the decision reversible?
07
Are we solving the underlying problem or only the visible symptom?
The goal is not to make every project bigger. It is to solve today’s need without unintentionally creating tomorrow’s constraint.
Independent advice. Practical execution.
The recommendation should fit the problem, not the provider.
I don’t resell software, earn commissions from vendors, or need to steer you toward a preferred platform.
That creates room to recommend what actually makes sense for your organization, including simplifying what you already have, doing less, or spending less.
Why TechEffective is differentSometimes the right answer is...
- Keep what you have.
- Simplify it.
- Fix the process first.
- Use the vendor you already have.
- Handle it internally.
- Bring in a specialist.
- Don’t spend the money yet.
And when the answer is to do the work
Advice doesn’t have to stop at the recommendation.
When hands-on work is the sensible next step, I can often help configure systems, improve integrations, clean up an implementation, troubleshoot problems, or move the project forward directly.
I’ve sat on both sides of the table
Advice looks different when you’ve had to live with the outcome.
I’ve spent more than 25 years working with technology, including 14 years in the nonprofit sector, both as an outside consultant and implementer and as the internal technology leader responsible for what happens next.
Inside the organization
I’ve been responsible for making it work over time.
As a nonprofit IT Director, I’ve owned budgets, systems, vendors, staff, projects, security, leadership expectations, and the long-term consequences of technology decisions.
Outside the organization
I’ve also been the person brought in to help.
I’ve worked as a consultant, implementer, developer, systems professional, and advisor helping organizations solve problems, make decisions, and deliver technology work.
I know the project isn’t over when the consultant leaves.
The solution still has to be owned, supported, explained, budgeted for, adopted by staff, and useful six months later. That perspective shapes how I approach the work from the start.
Start small
You don’t need a fully formed project to start a conversation.
Bring the situation, decision, concern, or idea you’re working through. We can figure out what kind of help would be useful, whether I’m the right person for it, and what a sensible next step might look like.
No obligation. No sales pitch. Just clarity.