
Pentangle is founder-led. Nick Constantine hears a problem in the language of the people who run the work and answers it in the language of the people who build it. He has lived on both sides: film, teaching, and advertising first, websites all along, then developer, software architect, and CTO. When you book a conversation, Nick is the one on the call, and when the work needs a specialist, he brings in one he trusts with it.
Who is Nick Constantine?
Nick Constantine is Pentangle's founder and the person who leads its work. He has been making things since he was a kid. He studied digital media arts and English at Michigan State, holds a secondary education degree, spent two years in film and two in advertising, taught, and built websites through all of it. Then he went deeper into the building side: a web developer and software architect for the better part of a decade, and a CTO after that.
That road matters because it taught him to pick up a new business quickly and see it from the shop floor, and because the skill he leans on most is translating between departments: finance and ops, ops and developers, ops and IT. You can read why Pentangle exists on the About page. The short version: tech debt has always been someone's second job, and Pentangle was built to make it the job somebody was brought in to do.
What has Nick actually built?
Two pieces of his work, from the years before Pentangle. For a die cutting company, he built an instant online quote tool on the formula that had lived in one estimator's head, so a customer got a price on the website the moment they asked. It worked: simple jobs never sat in the quote queue, complex ones still went to a person, and the shop ran with fewer people than other die cutting businesses for the same output. A large flooring company was set on a bloated middleware package that did not connect to its ERP natively; he offered to build a small integration, on its own server, that would do the job. They chose the middleware, paid far more in recurring costs, and still paid someone else to customize it. How does he know a project is working? When someone tells him their job is a lot faster with the tool, or when the KPIs come in better around the process he put in place.
That work is Nick's, from before Pentangle, and it set how he starts now: the first questions are about what you sell and how the work actually runs. The specialists he brings in depend on the project: a project manager, a developer, someone in dev ops or networking, a security specialist, a data engineer, an expert in machine learning or large language models, or, for a function or an industry, a specialist firm such as marketing or recruiting. Ask him about any of it on the call.
How does Nick run an engagement?
He hears the problem first, in the words of the people who live with it, then looks at the business as a whole before anything gets built. The naive-sounding questions come early on purpose; they surface the hidden workaround, the process only one department knows. Then the real issues get named, the projects get put in order, and the work starts.
Building starts with a first working version, then a constant feedback loop with the people who use it. You keep the final say on scope. If Nick thinks what you asked for should change, he says why, and you decide; if you still want your original path, that is what gets built. No rewritten specs. He is just as plain about build versus buy: he will not custom-build a big system without a strong reason, and where a real license saving exists, he points at it. A custom tool in place of a license for every technician? That's the job.

An engagement lands in one or more of these service lines:
- 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
- Data to value: automated reporting into one repository
- Headless systems: one pane of glass over several systems of record
Who works on your project?
Nick leads every engagement, and Pentangle brings in specialists he trusts as the work needs them. He is open about why: a generalist cannot match a deep specialist, and he does not pretend otherwise. What he carries is knowing who to bring in and putting your problem in front of them in your terms, so nothing is lost between the person who asked and the person who builds.
A specialist comes in for the piece of the work that needs them and not before, and the person who heard your problem stays the person leading the build. Specialists who work this way can reach Pentangle through the careers page.

Questions before you book
No. He has never specialized by industry. As a software architect he built for whatever business came through the door, and he gets to conversational knowledge of a new business quickly by asking the people who run it how it actually runs. The furthest behind, in his experience, are industrial companies: the IT was set up years ago, the business grew around it, and nobody has touched it since.
Nothing. The first conversation costs nothing and carries no obligation, and you talk to Nick himself. Bring the problem in whatever words your people use for it; that is the version he wants to hear. Book it through the contact page.
Yes. Auditing and refactoring apps built with AI tools is one of Pentangle's service lines. If someone on your team stood up a stopgap with an AI tool and the business now leans on it, Nick reads the code before giving any verdict on rewriting it. A code review for the app AI wrote? That's the job.
Book a conversation with Nick
Nick takes the call himself, and it costs nothing. Every company carries tech debt, even the biggest. That comes with growing. If yours has been waiting for things to slow down, you already know they never do. Bring the problem in your own words, and we will find a time that fits your schedule. Your tech debt. Our day job.