Hire or buy the result
Hire a person or buy a build
At Stackologists, a hire is a person in your stand-up and a build is a result on a date, and we keep them as separate contracts because blending them into one vague retainer is how both go sideways.
People often ask for “a senior full-stack person” when what they need is a finished API, or ask for “a project” when they already have a team and a backlog. Decide who owns the outcome and the contract mostly writes itself.
Say the outcome in one sentence
Before we open a match, we ask what has to be true after the next increment. If you can’t say it in one sentence, the contract isn’t ready yet.
- “A named Blazor or .NET person shipping in our process” → staffing.
- “This API, admin, or module works on a date we wrote down” → custom software.
- “Search can read the public routes we already shipped” → technical SEO.
Hire when the work is ongoing
Staffing fits when you’ve got a backlog, a stand-up, and someone who can review work. It’s extra capacity inside a system that stays yours. The stack list still has to be real: if the posting names six frameworks and the increment uses two, we match on the two.
You keep product ownership. The person works to your cadence, your PR rules, and your release train, and we review them against that cadence before anyone is introduced.
Signs staffing is the wrong ask
- Nobody can review their work for the first month.
- The “backlog” is really one unfinished project with no owner after handoff.
- You need a searchable public site next week more than you need a seat.
Buy a build when you need a finished piece
Think of an admin that replaces a spreadsheet, an ASP.NET Core API other teams can version against, a Blazor module with a finish date, or a public surface search can read. We own the result for a bounded window, and the handoff includes the decisions we made, not just the repository.
You review increments and we carry the delivery risk until the finish line in the agreement. If scope grows, the finish line gets rewritten before we keep coding.
Signs a build is the wrong ask
- You already have a team and only need capacity inside their process.
- You can’t describe the scope without inventing a second product.
- You want an open-ended retainer that soaks up every new idea.
Technical SEO is a third path
Sometimes the product exists and the public Angular or Blazor routes are empty shells. Then we start from the first HTML a crawler receives. It isn’t a content mill and it isn’t a ranking promise, and it isn’t staffing either unless you also want a person in the stand-up.
The trap: one vague retainer for both
Blending hire and build into one vague retainer hides who owns delivery risk, so we don’t sell it that way. Pick the path, write the outcome, and widen it later if the work changes shape.
After the contract is named, the stack leaf still matters — hire Blazor developers on Server or WebAssembly, hire .NET developers on the ASP.NET estate you run, or stay on Angular when that is already the product.