Your tech debt. Our day job.

"We'll get to it when things slow down." And the work never stops. Tech debt has always been someone's second job. That's why Pentangle exists. Bring us in, and you'll see your business and its technology on one roadmap, your people back on the jobs they were hired for, and your systems finally talking to each other.

The endless knot as rope, in cut paper

Technical debt in the wild.

Most companies build their technology a piece at a time, and every company carries tech debt, even the biggest. That comes with growing. What shouldn't: a twenty-person office still paying for paper and ink on its intake forms; a count keyed in twice; a quote waiting on the one person who knows the formula.

Those are the everyday ones. Deeper in the business, technical debt looks like this:

  • Two systems that have never talked, reconciled by hand
  • A software license paid per technician, where one custom tool would do
  • A process only one department knows, run its own way
  • An analyst's stopgap fix that quietly became the system
  • An app an AI tool wrote that nobody has reviewed or secured

Every one of these is somebody's second job, carried beside the work they were hired for.

The work

How do you reduce technical debt?

You reduce technical debt by making it the job somebody was brought in to do: look at the whole business, find the real issues, put the projects in order, then build the fixes beside the people who use them. Build a roadmap and pay down the debt over time. Technical debt reduction is Pentangle's whole practice, split into three services: technology strategy, business automation, and custom software, each laid out in full on our Services page.

  • Your business and its technology on one roadmap

    It starts with a look at the business as a whole, worked out beside whoever runs your technology today. You get the real issues found, a technology roadmap, and the projects put in order. No someday list. No fixes without the whole picture. No "it's always worked." For technical debt management with an owner in the seat, we do fractional CTO work and technology strategy consultation.

  • Your people back on the jobs they were hired for

    We find the manual work, or the one person a job waits on, and build the automation or system that takes it off their desk: an inventory count entered once, straight into the system, the day it is taken; a quote a customer gets online the moment they ask, with nobody filling in the formula. No keying it twice. No quote waiting on one person. The rest of our automation business solutions run on the same rule.

  • Your systems finally talking to each other

    You get the internal tools, custom software, and connections between your systems that you asked for, built to your spec; if we think it should change, we say why, and you decide. No rewritten specs. No tool nobody uses. You get a first working version, then a constant feedback loop with the people who use it. The same rules carry across our custom software, including auditing and refactoring apps built with AI tools.

Each service stands on its own; none of them obligates you to another. Start with whichever one is costing you the most.

A craftsman's workbench with its tools laid out in the order they are used

Who actually does the work?

Pentangle is one firm under one name. We lead the work ourselves, and specialists we trust are brought in as the work needs them, whether the week's work is discovery with your operations people or deep in the code. The firm that draws your roadmap is the same firm that builds what is on it, so you are never handed a diagnosis and left to staff the fix yourself.

We have sat in the CTO seat ourselves, and the practice here is that in-house job, done for you. We look at the whole business first, ask even the naive-sounding questions, and translate between departments: finance and ops, ops and developers, ops and IT. We are open about the limit of any generalist: a generalist cannot match a deep specialist, which is why knowing the right specialist, and bringing them in, is part of the service. You can meet the people behind Pentangle and how we work before anything is signed.

The work Pentangle stands on is our founder's own, from the years before the firm. For a die cutting shop, he built the estimator's quoting formula into the website, pricing jobs within about three percent of the estimator's own number. For a small therapy office of about twenty people, digitizing the paper intake forms saved $6,500 a year in paper and ink, and the hours counted for more: the front desk got more done, the paperwork came in clean and legible, which cut mistakes, and each therapist could see more patients a day.

Common questions about technical debt

No. A bug is a single failure you can fix and close. Tech debt is what keeps producing the same failures: the stopgap that became permanent, the two systems reconciled by hand, the leftover login nobody shut off. Recurring bugs? That's tech debt. A fix closes the ticket. The debt is the reason the ticket keeps coming back.

No. Pentangle is pragmatic about build versus buy: we do not custom-build a big system without strong justification, and where a custom tool saves direct license fees, we show that saving in dollars. The roadmap exists so each fix matches the problem it solves, with the whole picture in view. They quoted a full ERP to replace one intake form? That is the pattern a roadmap protects you from.

Owners, CEOs, and COOs whose growth leans on technology somebody set up years ago, and the private equity partners and board members behind them who decide who gets brought in to sort it out. We do not specialize by industry; we have built for whatever business came in, and we get to conversational knowledge of a new one quickly. In our experience the industrial companies run furthest behind, and our founder tells the scene we keep meeting: somebody's nephew set up the email, or somebody's brother-in-law put in the network and never touched it again, and ten years later the company is huge. A company fresh off an acquisition, still running every system it arrived with, fits this work exactly.

Start with a conversation

Most companies, even big ones, run on tap-you-on-the-shoulder-and-ask processes. That is human, and it is a big part of why industrial companies work. But to scale, that humanity needs efficiencies built around it. Bring the job that waits on one person, the count keyed twice, or the acquisition still running its own systems, and we hear the problem in your own words before we propose anything. If we think the plan should change, we say why, and you decide. Nobody is talked down to, and nobody is sold a system bigger than the problem. Your tech debt. Our day job.

An old telephone switchboard with its cords patched in neatly