An old film camera on a tripod beside a drafting compass and a coiled rope, the tools of one varied road

About Pentangle

Tech debt has always been someone's second job.

You know the company is carrying tech debt. What you do not know is who to hand it to without being talked down to or sold a whole new system. That handoff is what Pentangle is for. Tech debt has always been someone's second job, carried on the side of a full day. "We'll get to it when things slow down." And the work never stops. Here, it is the day job, and the work covers:

  • Technology roadmaps
  • Fractional CTO work
  • Technology strategy consultation
  • Business automation
  • Internal tools and custom software
  • System integrations
  • Auditing and refactoring apps built with AI tools

Who you are handing it to

You are handing it to Nick Constantine, Pentangle's founder, and to the specialists he trusts, brought in as the work needs them.

What Pentangle does

Pentangle does three things. We put your business and its technology on one roadmap, we get your people back on the jobs they were hired for, and we get your systems finally talking to each other. These are the three ways we help, and each stands on its own as its own engagement; none of them requires buying another.

Your business and its technology on one roadmap

You get a technology roadmap built from a look at the whole business: the real issues found and the projects put in order, worked out beside whoever runs your technology today. Nobody loses a seat; the CTO keeps their job and the engineers stay on what ships next. The same look drives our technology roadmap consulting and our fractional CTO and technology strategy work, where you get the CTO seat for the part of it you need. No someday list. No fixes without the whole picture.

Your people back on the jobs they were hired for

You can bring us in to find the manual work, or the one person a job waits on, and we build the automation or the system that takes it off their desk. That looks like an inventory count entered once, straight into the system, the day it is taken, or a quote a customer gets online the moment they ask, with nobody filling in the formula. No keying it twice. We price these wins in hours handed back, including hours handed back to people who never touch the new system.

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. If you keep your original path, we build your original path. That rule comes from our founder's own years as the client, when he handed a firm a spec and they would not spec out what he asked for. A first working version goes in front of the people who use it, then a constant feedback loop. We also audit and refactor apps built with AI tools. A code review for the app AI wrote? That's the job.

One firm, one name on the work

You buy from Pentangle, and our founder answers for the work. A generalist cannot match a deep specialist, and we say so ourselves; our answer is knowing which specialist to bring in and when, while the engagement stays ours to answer for. The advice stays straight on build versus buy: a big custom system needs strong justification before we will build it, and where a custom tool replaces a software license paid per technician, we show the saving in dollars. When your request is not what we think you need, you hear why first, and your call stands.

An engineer's toolbox standing open, its tools in their places and one fine precision instrument laid beside it

Questions owners and their backers ask

An IT strategy consultant looks at how the whole business runs, finds the real technology issues, builds the roadmap, and puts the projects in order so the money goes to the right project first. At Pentangle that look includes the naive-sounding questions, starting with what you sell, because discovery keeps finding the process only one department knows and folding it into scope.

Ask what they looked at before they named a fix. They asked about your servers and never once what you sell? If that scene sounds familiar, put the next firm to a plainer test: what do they want to understand first, who sits in the discovery sessions, how do the projects get their order, and will they build your plan when you decide to keep it. We answer those the same way on every job: the business first, the operators in the room, reasons and dollars on the order, and your call standing at the end.

Owners, CEOs, and COOs of companies 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. We do not pick one industry. Our founder spent his architect years building for whatever business came through the door, and we get to conversational knowledge of a new company quickly. The company we keep meeting is industrial: the IT set up years ago, never touched again, and the business now grown past it.

Bring us the thing that is stuck

Most companies build their technology a piece at a time, and every company carries tech debt, even the biggest. That comes with growing. What should not come with it is the count keyed in twice, the quote that waits on one person, or the two systems that have never talked. Pick the one that costs you the most and talk to us about it.