Category
110 articles in Business.
About this section
The commercial side of running and buying software, written from inside an agency rather than from a consultancy deck. That means the numbers here are specific and occasionally awkward: what agencies actually charge and why, where a fixed-price quote goes wrong for both sides, how to read a proposal, and what a developer or engineer is genuinely worth in a given market. A good portion is aimed at the person doing the buying rather than the building, because most bad software outcomes are decided before any code is written, in a scoping conversation that nobody wrote down properly. We would rather publish the parts our own clients ask about in month three than keep them as sales material.
All 110 articles
P.01A good Django hire reads the ORM's SQL, knows the support calendar and treats settings as a security surface. A screening plan with tests you can run.
P.02Switching agencies or freelancers? Get repo, cloud, app store and domain ownership in your name first, then audit the code. A step-by-step handover list.
P.03How to hire a developer to audit an app built with an AI tool: what the audit covers, what the report must contain, and how to judge the quote.
P.04Hiring a freelancer or agency does not make you the owner of the code. What the law defaults to in the US and India, and the clauses that fix it.
P.05A paid trial project of 20-40 hours on real backlog work tells you more than any interview. How to scope it, pay for it and score the result fairly.
P.06Next.js 16 changed what 'knows Next.js' means: Turbopack, Cache Components, and Server Actions by default. What to screen for, and the questions that reveal real skill.
P.07IBM's 2026 report puts the average breach at $4.99M. Pentests run $4K-$30K, IR retainers $25K-$150K a year. Patching early is the cheapest line item.
P.08Copilot Business and Enterprise require prepaid per-seat billing from October 1, and promotional AI Credits already reverted. What agencies should budget for.
P.09A solutions architect posting attracts cloud generalists, ex-consultants, and people who haven't shipped in years. How to tell them apart, and what to test.
P.10PM job descriptions read identically across companies. The actual job doesn't. Which of the three real PM jobs you're hiring for, and what the role costs.
P.11Shopify hiring split into two jobs, theme customization and app or headless work, that share a platform and little else. How to tell which one you need.
P.12Firmware hiring fails differently from web hiring. The pool is small, the specialisms don't transfer, and the usual coding screen tells you almost nothing.
P.132026 rate data shows two opposite trends: AI-assisted competition pushing junior rates down while seniors who can supervise AI output command more than ever.
P.14Deployment frequency, lead time, change failure rate, time to restore. What each measures, the tiers that separate elite teams, and where teams misuse them.
P.15Oracle cut about 21,000 jobs in FY2026 while AI data center capex nearly tripled to $55.7B. The math, and what it should change about your OCI vendor risk.
P.16Braintrust's pitch is that talent keeps 100% and the fee sits with the client. That changes the incentives in ways worth understanding before you decide it is cheaper.
P.17Andela suits companies adding sustained engineering capacity across timezones. If your need is smaller or shorter, the enterprise shape works against you.
P.18Turing is built for long, full-time-equivalent remote engagements matched by an algorithm. What that suits, and where to look when the shape is wrong.
P.19A data analyst is not a junior data scientist or a dashboard builder. What the role requires, how it differs, and the screen that finds decision-changing work.
P.20Most agencies keep a bad client months too long because nobody has a framework. How to recognise when it's time, and how to end it without burning bridges.
P.21EM hires fail for different reasons than IC hires. What to actually test: handling underperformance, technical debt calls, and pushback with the business.
P.22Game hiring is not web hiring. How to tell Unity talent from Unreal talent, what to actually test for, and what it costs to get this right in 2026.
P.23Calculate sample size before you start, from your baseline rate and the smallest effect worth detecting, then run to it. Stopping early gives you noise.
P.24Article 50 requires AI disclosure for chatbots, machine-readable marks on generated media, and deepfake labels. A checklist of each duty, its dates and fines.
P.25Looking for an Arc.dev alternative to hire vetted remote developers? What Arc.dev does well, where it leaves work on your plate, and how the options compare.
P.26Gun.io is strong for senior US-timezone freelancers, but it isn't the only way to hire vetted developers. The real alternatives, and how to choose between them.
P.27Looking for a Lemon.io alternative to hire vetted developers? Where Lemon.io fits, where it doesn't, and how to choose for the role you're actually filling.
P.28Upwork is the biggest freelance marketplace, but the vetting is on you. An honest look at Upwork alternatives for developers and how to pick the right one.
P.29Angular's enterprise comeback is real. Signals, standalone components, and zoneless change detection changed what senior skill looks like. How to hire for it.
P.30DevSecOps is distinct from DevOps and from security engineering. What the role covers, what to screen for, and why supply chain security is now the core.
P.31Svelte 5 runes changed the reactivity model in ways that matter for hiring. The pool is small but experienced. How to find, screen, and evaluate them.
P.32A database engineer designs schemas and tunes queries; a data engineer builds pipelines. How to screen for the one who keeps your app fast, plus 2026 rates.
P.33React Native's New Architecture is the default now. Screening for JS and native boundaries, Expo tradeoffs, and knowing when cross-platform is wrong.
P.34Salesforce runs sales and service for 150,000+ companies. The wrong developer means expensive tech debt inside a platform you can't easily migrate off.
P.35WordPress runs 43% of the web, but the title covers everyone from theme configurers to block API engineers. How to find one who builds what you need.
P.36How to assess a codebase before you buy, inherit, or partner on it: the documents to request, what kills deals, and what turns out to be fixable.
P.37Blockchain developer is four jobs: smart contract, dApp frontend, protocol, and security auditing. Each needs a different screen. How to find the right one.
P.38C++ covers game engines, embedded, high-frequency trading, and infrastructure. The skills that matter change completely with what you're actually building.
P.39Elixir's talent pool is small, opinionated, and genuinely skilled. How to find the real engineers in it, and why the screen differs from other backend hires.
P.40SRE is a discipline, not DevOps with a pager. How to define the role, screen for reliability math, and avoid hiring an ops generalist by accident.
P.41The order you hire your first 10 engineers matters more than the headcount. How to sequence the hires, what ratios work, and the mistakes that slow teams.
P.42Mobile app budgets get underestimated because they only price the build. A full cost breakdown by app type and platform, plus the hidden line items.
P.43Cloud architect is a badly misused title. How to define the role, screen for real judgment, and avoid hiring a certification collection by mistake.
P.44Security engineer covers five genuinely different jobs. How to define the one you need, run a screen that tests real skill, and dodge the usual mistakes.
P.45The product designer role consolidated in 2026. How to write the job post, read portfolios honestly, and screen for designers who can actually ship.
P.46Most software RFPs draw no responses or bad ones. What belongs in the document, what to leave out, and how agencies decide whether to reply at all.
P.47Data scientist and ML engineer are two different jobs. The distinction, what a strong data scientist does, and how to screen for real analytical judgment.
P.48Frontend developer means different things to different teams. The core screen: HTML semantics, CSS fundamentals, Core Web Vitals, and skill beyond React.
P.49Kotlin is the default for Android and growing on the JVM backend. What to screen for, how Kotlin skills differ from Java, and what the role really needs.
P.50QA is risk thinking, not script writing. What a strong QA engineer brings, what to test in the interview, and how to avoid hiring a regression-suite runner.
P.51Most hiring managers look at the wrong things. Stars and followers tell you almost nothing. What to look for, and what AI changed about reading profiles.
P.52AI engineer is not ML engineer. One trains models, the other builds products on them. The screen that tells them apart and finds people who actually ship.
P.53The .NET platform changed more in three years than the decade before. What a strong .NET developer looks like now, and what marks a 2015 mindset.
P.54Java 21 brought virtual threads; Spring Boot 3 needs Java 17. Most job posts still test for Java 8. What a strong Java developer actually looks like now.
P.55Flutter dominates cross-platform mobile now, and the gap between tutorial-complete and production-shipped is wide. The screen that finds the difference.
P.56Everyone claims ML experience since the AI boom. The screen that separates people who ship ML systems from people who fine-tuned once in a Colab notebook.
P.57PHP runs most of the web and the pool is huge, which makes it easy to hire someone who knows PHP and hard to hire someone who can actually build with it.
P.58Rails 8 changed the deployment and infrastructure story. A developer who kept up looks different from one working off 2019 knowledge. What to screen for.
P.59Rust is growing in backend, systems, and WASM. The challenge is telling developers who understand ownership from those who just fight the borrow checker.
P.60Vue 3 is the default now and the Options API is legacy. What a strong Vue developer looks like, what questions reveal real skill, and the red flags.
P.61Both formats have real problems, and AI made take-homes worse. What each predicts, where each fails, and the hybrid that beats either one on its own.
P.62Most reference checks are theater: three friends say nice things and you move on. How to run calls that surface real information before you make an offer.
P.63Data engineers build the pipelines, warehouses, and transformation layers. They aren't data scientists, backend developers, or analysts. How to hire for it.
P.64Go runs Kubernetes, Docker, Prometheus, and most cloud tooling. What the language attracts, what it demands, and how to screen for the right profile.
P.65TypeScript is the default now, so the market is full of people who write it without understanding it. The questions that tell the two groups apart.
P.66Full-stack means something different to every team. How to define what you need, catch specialists in disguise, and know when a generalist is the right call.
P.67Node.js has split into async-first, TypeScript-native, and edge-runtime camps. The screen that finds someone who builds production backends, not tutorials.
P.68Choosing the wrong contract structure reliably damages a client relationship. A practical guide to SoW, T&M, and the hybrid models that actually work.
P.69The DevOps engineer title now covers three jobs: platform engineer, SRE, and CI/CD specialist. What each does, what to screen for, and what the market pays.
P.70iOS changed more in three years than the previous seven. What strong candidates actually know, how to screen for it, and what to expect on rates.
P.71LeetCode interviews are popular and mostly useless for predicting on-the-job performance. What the research says works, and how to build that process.
P.72Android changed more in three years than the prior decade. How to tell who builds modern Compose apps from who learned it in 2019 and stopped there.
P.73Python spans AI, data, backend, and DevOps, so the title says little. How to define the role, screen for real ability, and avoid a costly mismatch.
P.74A week-by-week playbook for onboarding a new software engineer. What to cover in the first month, what most teams skip, and how to measure whether it is working.
P.75A step-by-step guide to screening React developers in 2026 — what to test, what seniority looks like, and the red flags that save you from a bad hire.
P.76I run one, so here's how to hire one, including the parts most agency owners would rather you didn't know. Green flags, red flags, partner versus vendor.
P.77Everyone says their developers are vetted. Almost nobody says what that means. What real vetting looks like, the screen we run, and the red flags to catch.
P.78Comparing offshore, nearshore, and onshore development for staffing a project: what each model costs, where each one breaks, and how to actually choose.
P.79Most technical job descriptions repel the people they're trying to hire. What senior developers actually look for, and how to write a posting that lands.
P.80Want Toptal-level vetting without the premium? Marketplaces, agencies and AI-screened shortlists cost less and still vet developers. What each trades off.
P.81The salary is the smallest part of the answer. A framework for the real cost of in-house, freelance, agency, and managed hiring, so you budget the total.
P.82AI has cut development time, but not what software is worth. Here are three pricing models, value-based, output-based, and capacity retainers, for agencies.
P.83Agency IP productization turns rebuilt code into recurring revenue: how to spot what's worth extracting, pick a packaging model, and price it.
P.84Most agency owners are the bottleneck in their own business. Here's how to build systems for client work, hiring, and operations that run without you.
P.85Standard Scrum assumes stable backlogs, but agencies face client reviews, scope talks, and projects that end. Here's the adapted sprint structure that works.
P.86Most agencies figure out support pricing and SLA structure only after a client calls at 11pm. A better approach: define what you're selling before the project launches.
P.87When AI tools write 40-70% of a codebase, familiarity-based maintenance pricing breaks. Here is how to audit and price support work you didn't fully write.
P.88Most agency case studies fail because they document process instead of the client's decision and what changed. The structure that converts, and what to cut.
P.89Hiring full-time for a three-month surge is one of the most expensive agency mistakes. How to build a contractor network before the moment you need it.
P.90Most software estimates fail before code is written, not from bad hours but unexamined assumptions. Here is a more honest, process-driven estimation approach.
P.91Most handoff docs get ignored once a client can't find their CMS login. What to write, how to structure it, and what agencies skip that causes support calls.
P.92How to structure agency payment terms: deposits, milestone billing, net terms, and late fees that keep cash flow predictable and overdue invoices rare.
P.93Manually compiling monthly client reports is high-effort, low-value work. Here's how to automate the data collection and drafting while keeping a human in the loop.
P.94Most agencies invoice and move on. The ones that improve fastest sit down and ask what actually happened. How to run a debrief that produces changes.
P.95A spec that doesn't get signed protects no one. Here's how agencies structure technical specifications that move projects forward instead of stalling them.
P.96Scope creep looks like a client problem until you notice the same clients cause it every time and others never do. The difference is process, not personality.
P.97AI contract clauses on IP, hallucination liability, and data deletion trip up agencies before they sign. Here's what each clause means and how to rewrite it.
P.98Every agency hits the same wall: more work than the team can handle, not enough volume for a hire. White-label partnerships are how survivors manage growth.
P.99Most agency developers never check the licence of an npm package until a client's lawyer does. What MIT, Apache 2.0, GPL and AGPL actually require.
P.100Retainer contracts promise stable revenue but often create scope creep and capacity problems. Here's how to structure retainers that work for both sides.
P.101The wrong project start leads to scope creep and a client who stops responding. Here's the 30-day onboarding process we use to win agency relationships from day one.
P.102Most technical proposals lose because they describe what will be built, not why the client should trust you to build it. Here's how to write one that actually wins.
P.103Most AI project failures start at scoping: nobody defines what 'AI integration' means before a price is quoted. Here's how to scope AI projects properly.
P.104Every AI budget starts with API costs and ends in surprises. What production AI features really cost once evaluation, observability and prompt rot are counted.
P.105Fixed price puts the risk on the agency; time and materials puts it on the client. Here's how to decide which contract model actually fits your project.
P.106Real revenue, profit margins, and owner take-home for solo, boutique, mid-size, and enterprise web agencies, including the messy parts most income reports skip.
P.107Every engineering team faces build vs buy decisions constantly. Here's a practical framework for making these decisions without analysis paralysis.
P.108Measuring developer productivity is notoriously difficult. DORA and SPACE frameworks offer research-backed approaches, but implementation is where most teams fail.
P.109Remote work is permanent. Here's how to hire, onboard, and manage distributed engineering teams across time zones, cultures, and employment structures.
P.110Choosing a tech stack is one of the earliest and most consequential decisions for a startup. Here's a practical guide to making choices you won't regret.