Recent Insights.

Some of the best organizations we've worked with have websites that undersell them badly. Great reputation in the room. Real outcomes. And a homepage that reads like it was written by committee, because it probably was. If a total stranger read your website today, with zero context on your reputation, would they come away as convinced as the people who already know you? Reply if you actually know the answer. We're guessing a lot of people are about to go check.

Said this in a client call and it's stuck with us since. We asked what success would look like for their new site, and the answer was "more traffic." We pushed a little. Traffic to do what? More people reading the blog, or more of the right people filling out the contact form? Those aren't the same goal, and they don't get built the same way. Most organizations never separate the two before a project starts, so at the end they measure whatever's easiest to pull a number for, whether or not it means anything. Worth asking before the next project starts, not after it wraps.

A website that gets handed off at launch starts decaying the same day. Not because anything breaks. Because nobody's watching it anymore. The content goes stale, the workflow that got documented once stops getting followed, and small problems pile up quietly until they're not small anymore. We think ongoing support beats project-based work for most organizations, not because it keeps a consultant involved longer, but because someone is actually paying attention on a regular cadence. Things get caught while they're still cheap to fix. Tell us where this is wrong. Genuinely curious if anyone's seen a one-and-done project age well.

Things that should probably not require a web developer in 2026. × Fixing a typo in your pricing table × Swapping out a team photo from three years ago × Adding a new phone number × Updating a broken link someone finally noticed × Changing the color of a button × Uploading a PDF × Getting sign-off from three different people before any of the above happens Every website setup is different, and some things really do need technical help. But if your own team hesitates to touch your own website, that's not a skills problem. That's a system someone built to keep them out of it. What's the smallest change on your site that somehow takes the longest to get approved?

If you've been thinking about reaching out and haven't yet, this is for you. A 15-minute discovery call with us isn't a pitch. It's a conversation that ends with you knowing three specific things more clearly than when you started. One: what the actual problem is. Not the presenting version. The one underneath. We're good at finding it fast. Two: what fixing it is realistically going to take. Not a sales answer. A real answer about scope, sequencing, and what gets addressed first versus what can wait. Three: whether we're the right fit to help. We'll tell you directly. If we are, we'll say what a first step could look like. If we're not, we'll tell you what kind of help would actually serve your situation. Most people leave the call saying they wish they'd had it sooner. Not because we convinced them of anything. Because they came in with a fuzzy sense of a problem and left with a clear one. That's a useful 15 minutes regardless of what comes next. The Calendly link is in my profile. Or reply here if you'd rather start with a message. I read everything.

We get asked sometimes what we'd do if we were in our clients' position. Here's an honest answer for leaders at small to mid-sized organizations working through a digital challenge. We'd stop trying to fix everything at once. The organizations that make the most progress tend to pick the one thing that, if it were working, would make the most other things easier. Not the most visible problem. Not the one that's been on the list the longest. The one with the most downstream leverage. Usually that's the communication foundation. How the organization describes itself. The language that shows up consistently across the website, in proposals, in client conversations, and in team meetings. When that's inconsistent, everything built on top of it is less effective than it could be. We'd also stop treating the website as a separate problem from the communications. They're almost always the same problem wearing different interfaces. And we'd have a real conversation about what "done" means before committing to any project. Not what will be delivered. What will be different about how the organization operates when it's done. That one question changes everything about how the project gets scoped. If you want to have that conversation about your specific situation, we're easy to reach. A 15-minute call costs nothing and usually moves things.

One of the harder parts of getting digital work done isn't finding the right partner. It's making the case internally. If you're a leader who needs board approval, a co-founder's buy-in, or a committee's sign-off before moving forward, the conversation can feel harder than the project itself. A few things we've seen work when leaders build this case. Start with the cost of the current situation, not the cost of the project. A board will approve a budget for a solution faster when they understand what the broken version is costing in staff time, missed inquiries, or reputational erosion. Get specific about what "fixed" looks like. Vague goals lose votes. "Clients will be able to find our intake information without calling the office" is a goal people can picture and support. Separate the phases. A full engagement doesn't have to be approved all at once. A discovery phase is a small, scoped commitment that produces a clear picture of the work ahead. It's a much easier internal ask than approving an entire project sight unseen. We've helped leaders frame this case before. If you're trying to build it and want a thought partner, a 15-minute conversation with us would give you the language and framing you need. That's a useful outcome even if we never work together.

"It's not the right time." We hear this more than almost anything else. And we understand it. Things are busy. The budget isn't where it needs to be. The team is in the middle of something else. But in our experience, the organizations that say it's not the right time aren't usually waiting for the right time. They're waiting for the feeling that things are settled enough to take on something new. That feeling rarely comes on its own. The organizations that move forward almost never do it because everything cleared up. They do it because they decided that the cost of staying where they are was higher than the uncertainty of making a change. That's a different calculation than "is the timing right." It's "what is this actually costing us to leave broken, and how long are we willing to pay that?" We've worked with organizations in the middle of leadership transitions, budget crunches, staff changes, and program pivots. The projects that went best during those periods weren't the ones we did despite the timing. They were the ones where the client decided that getting the foundation right was the thing that would make the hard period more manageable. If you've been waiting for the right time, we'd be glad to think through what you're actually waiting for. That conversation is free, and it might save you another six months.

Sometimes we read a client's brief and know that what they're asking for won't solve the problem they're describing. Not often. But it happens. A nonprofit wants a new website. The brief describes the site they want. But what they've described doesn't address the fact that their messaging has three different versions depending on who you ask, and no design will hold that together. A business wants a workflow solution. But the workflow problem turns out to be a communication problem that predates any system they've used. When we see this, we say so. Directly and early. We show the gap between the presenting request and the underlying problem. We explain what we'd recommend instead and why. This conversation isn't always comfortable. Clients come in having already decided what they need, and being told "that's not quite the right starting point" takes some trust to hear. But we'd rather have that conversation in week one than six weeks into a project heading in the wrong direction. The clients who've been through this with us consistently say the same thing: they appreciated that we said something. And the work that came out of it was better because we started from the real problem. This is the kind of conversation we're good at having. It's part of what makes the work worth doing.

There's one question we ask every client in the first week of an engagement. It's not "what do you want the website to look like?" or "who is your target audience?" Those come later. The question is: "If this project went perfectly and we were talking six months from now, what would be different?" The answer is almost never about the website. It's almost always about something underneath it. The team would stop getting calls from clients asking for information that should be on the site. Funders would understand the organization's work without needing a follow-up meeting. A new hire would be able to onboard without asking the same questions to six different colleagues. The gap between what people say they want (a better website, a cleaner workflow) and what they actually want (less friction, more clarity, work they can be proud of showing people) is almost always there. And the answer to this question is usually where it shows up most clearly. We build the engagement around the real answer. Not the presenting request. What would your answer be?

Most organizations that reach out to us have more than one thing broken. The website needs attention. The internal communication is inconsistent. There's a workflow that's been on the list for a year. And the team doesn't agree on how to describe what they do. The question isn't whether all of it needs fixing. The question is what to fix first. Here's how we think about it. We look for the thing that's creating the most drag. Not the most visible problem. Not the one that's easiest to fix. The one that's slowing everything else down. Usually, it's a communication problem at the core. If the team doesn't have a shared, clear way to describe who they serve and what they do, the website can't say it clearly either. And workflow problems often turn out to be communication problems wearing operational clothing. Fix the communication foundation first, and a lot of the downstream problems become easier or resolve on their own. Fix the downstream problems without touching the foundation, and you'll be back in the same place in 18 months with different symptoms. The starting point matters more than the speed. If you want to talk through what the starting point might be for your organization, that's exactly what discovery conversations are for.

Most proposals from digital agencies or freelancers tell you what they'll build and what it will cost. What they usually don't tell you: why they chose that scope, what they're assuming about your situation, and what happens if those assumptions turn out to be wrong. That's a significant gap. When a proposal arrives with the approach already fully formed, it usually means one of two things. Either the agency has done this particular type of project so many times they know exactly what it requires, or they're fitting your situation into a template because that's faster than thinking it through from scratch. Both happen. The first is fine. The second can get expensive. A proposal worth taking seriously should show its reasoning. Not just the deliverables, but the thinking behind why those deliverables address your specific situation. If the proposal would look nearly identical for a different organization with a different problem, that's a signal worth paying attention to. We build our proposals around what we hear in the discovery conversation. Every scope is specific because every organization's situation is specific. If you're evaluating a proposal for digital work right now and something feels off about it, we're happy to take a look and tell you what we see. No obligation, no pitch.