What You Don't Know You Need Costs More Later

We hear it often: there are tech partners and outsourcing locations cheaper than Softjourn. We agree, you can find someone cheaper. This is a story about the one time we were that cheaper option ourselves, and what it actually cost.

The Decision We Made

A client came to us with a tight budget and a track record that had already given us some pause. Rather than pass on the engagement, we made an exception. We negotiated one of our developers' rates down to fit the client's number, and moved forward.

That decision – not the rate itself, but the choice to bend on it for a client we already had reason to be cautious about – is really what this story is about. It came with a second decision attached to it, one that got far less attention at the time: no project manager sat between our developer and the client day-to-day. That role is usually what catches drift early, before the work starts moving away from what was actually agreed. Nobody was in a position to notice the pattern until it was already well established.

What Actually Happened

The agreement with this client was to bring in a senior developer to build a specific feature. Nine working days in, that feature still hadn't been started. This wasn't on our developer: requests were arriving through more than 30 different channels, and each new one took priority over the last. Nobody made a single decision to reassign the work; it just drifted, one urgent request at a time, until firefighting had quietly become the job our senior developer was actually doing.

When he finally got time to build the feature he'd been brought in for, it turned out to already exist, in a rough, tangled first pass, an AI-assisted attempt written by one of the client's own junior developers, with little structure holding it together and no real plan behind how the pieces connected. What had been scoped as new development was really an audit and repair job, on code nobody had planned for him to inherit.

Two Kinds of "We Move Fast"

Not every fast-moving startup environment looks the same up close, even though most of them get pitched the same way going in ("wear many hats, move fast"). Some are healthy: priorities shift constantly, and a good team juggles it with real organization and communication – demanding, but sustainable. Others are unhealthy: nothing is clearly defined, documentation doesn't exist, and whoever's available simply absorbs whatever lands next.

"We move fast" and "we're a startup" can describe either one. The only way to tell them apart before you commit is to ask. If a client tells you to expect a fast-moving environment, ask what that actually looks like on a normal week. Ask for an example of a week that went sideways, and what happened after. It usually tells you more than the pitch does.

What It Actually Cost

None of this was caused by the discount on its own. It was caused by the discount plus the two decisions that came bundled with it: taking on a client we already had doubts about, and not putting a project manager in place to catch the drift while it was still small.

Each choice made sense in isolation. Made together, they meant nobody caught the problem until a senior developer had spent two weeks on work he wasn't hired for, and a feature still didn't exist.

What We Do Differently Now

We still make judgment calls on rate and risk. That hasn't changed, and it shouldn't. We'll still consider a client's budget, still negotiate, and still take on engagements below our standard fee when it makes sense to.

What's different now is what we pair those calls with. When we take on more risk on one side of an engagement, a lower rate, a client we're still building trust with, we don't also strip away the safeguards, like a project manager on the account or a proper discovery phase before we commit, that would normally catch problems early. Rate and safeguards get weighed together now, not one after the other.

Final Thoughts

Cheaper providers exist, and for one project, we were one of them. We've written before about what that trade costs a client, a two-month estimate that became a ten-month ordeal. This time, the cost landed on us.

If you're weighing a lower rate against what a role actually requires, we're happy to talk it through before you commit either way.