Business automation

Your quote that waits on one person. Our day job.

An antique cash register with its price flags raised, the price there the moment it is asked

A quote tool built on the formula in your estimator's head? That's the job. We build automated quoting systems: the inputs your estimator asks for, the margins they hold, the exceptions they know by feel, turned into a price your customer gets online the moment they ask, with nobody filling in the formula.

It is built for the owner or COO whose prices still queue behind one calendar, and for the partner behind them who wants it fixed without adding headcount.

When every quote waits on one person

Most companies build their technology a piece at a time, and every company carries tech debt. That comes with growing. What shouldn't: a quote waiting on the one person who knows the formula. A request comes in while that person is on a job, out sick, or two weeks deep in a backlog, and the customer waits with it. Anyone in the office can take the call; only one person can give the number. Fixing it has always been somebody's second job, carried on the side of a full desk.

A price your customer gets the moment they ask

An automated quoting system puts the answer on your website: a customer describes the job, the formula prices it, and the quote is in their hands while they are still looking at your site, whether your estimator is in that day or not. Our case for the work is plain: how fast a business can give a price and send an invoice drives revenue. No keying it twice. No quote waiting on one person. No fixes on your people's own time. An instant quote is one of the automation business solutions we build, and every one of them aims at the same end: your people, back on the jobs they were hired for.

A mechanical calculating machine printing a price ticket as the crank turns

How the build works

We hear how a price really gets made, write the formula down, prove it against your own past quotes, and put a working version in front of the people who will use it. In order:

  1. Discovery.We sit with your estimator and whoever else touches a quote, and hear the problem in your own words: the inputs, the margins, the exception one department handles its own way.
  2. The formula, written down.The rules come out of the spreadsheet and the estimator's head and into the system, and we check its numbers against quotes you have already sent.
  3. A first working version, then a constant feedback loop with the people who use it.
  4. Built to your spec.If we think a piece of it should change, we say why, and you decide. If you still want your original path, we build your original path.

The quote tool is its own engagement, and nothing else is attached to it. Where the request itself still arrives on paper, digital intake forms are a separate fix, built the same way: hear it in your words, build it to your spec.

Should you buy quoting software or build your own?

Buy it when a tool off the shelf already prices the way you price. We are pragmatic about build versus buy; we do not custom-build where a bought tool does the job, and discovery is where we say which this is. The case for building is the formula itself. A packaged tool has to serve every kind of shop, so quoting software for small business starts from its own template: your pricing has to fit its fields, and the parts that do not fit stay where they have always been, in the estimator's head. And if quoting turns out to be one bottleneck among five, you may want a fractional CTO to prioritize the whole roadmap before anything gets built.

Built so three people could run a die cutting business

Our founder's first instant quote tool was built for a die cutting business whose pricing lived with one estimator. The estimator's formula had human checks built into it, so our founder cut a couple of the variables and generalized others until the tool priced within about three percent of the number the estimator would have come up with, and a customer got a price the moment they asked, straight from the website. Once it went live, it worked, and it did exactly what it should. Jobs came in with quotes; the simple ones never sat in the quote queue, and the complex ones still went to a person to review. The shop ran with fewer people than other die cutting businesses, for the same output. Pentangle grew out of that build, and it set the bar this work is held to: a number the estimator himself can trust, from the website, at any hour, in a shop with three people and no spare hands for paperwork.

Who does the work

Pentangle is its founder and the specialists we trust, brought in as the work needs them.

Brass gears of different sizes meshing together, each one turning the next

We have spent years building web software and sitting in the CTO seat, with a career's habit of translating between finance, operations, and the people writing the code, so your estimator will never have to speak developer. Your point of contact is domestic. And because the firm is built around the work, you are not adding a seat to get the quote fixed; you are handing the job to people brought in to do exactly that job.

Start with discovery

The first step is a call and a discovery session, and nothing gets built until you have seen what we found and agreed on the scope. We map the formula with the person who owns it, check it against quotes you have already sent, and put the work in order before a line of it is built; if a bought tool would do the job for less, that is what you will hear. When the quote is the bottleneck, bring us in to take the quote off one person's desk.

From the first spreadsheet to the full ERP, your tech debt. Our day job.

Questions owners ask before they build

Straight answers to the questions that decide whether this build makes sense.

Yes, and if one person prices a handful of jobs and nobody waits on them, a spreadsheet may be all you need. Its limit is who can use it. A spreadsheet prices a job for whoever has the file open; it cannot hand a customer a price from your website after hours, and the formula still travels with one person. Spreadsheet passwords? That's tech debt. When you outgrow it, the spreadsheet is not wasted: it is the formula, already written down, and the build starts from it.

Exceptions are the reason to build on your formula instead of forcing it into a template. Discovery exists to find them: the rule one department applies its own way, the adjustment your estimator makes by feel, the workaround nobody wrote down. Each one is either written into the formula or kept as a human decision, and you make that call with the whole picture in front of you. Before the system quotes a real customer, its numbers are checked against quotes you have already sent.

Yes. We do not specialise by industry. We have spent years building for whatever business came through the door, and what we have seen is that the industrial trades, construction among them, run especially far behind on technology. The build does not change with the trade; the formula does, and the formula comes out of your estimator's head. If your estimator prices from a walkthrough, a takeoff, or a spreadsheet of unit costs, that is exactly the material discovery works from.

Yes. Auditing and refactoring apps built with AI tools is one of our service lines. We open the code before we judge it, keep what holds, and fix what does not; if the right call is to rebuild on your estimator's formula, we say why and you decide. A stopgap that mostly works is a head start, and whoever built it knows your quoting better than any outsider, so discovery starts with them.

The honest answer is that the price follows the formula, and discovery is where it gets sized; we will not pretend a number before we have seen the formula. Two things hold either way. We are pragmatic about build versus buy, so if a bought tool or the spreadsheet you already have is the right answer, that is the answer you get. And the scope covers the quoting problem alone, with nothing else attached.