Your people back on the jobs they were hired for

A clockwork machine stamping a stack of papers on its own

Somewhere in your company a count taken on paper is keyed in again at month end. A quote sits because the one person who knows the formula is out. A form gets printed, signed, and typed back into the same system it came from.

That is the work Pentangle exists to take. 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. We do not hand your team a license to configure and babysit. We hear the problem in your people's own words, build the thing, and hand it over working.

What is business process automation?

Business process automation is software that does a routine task the moment it happens instead of a person doing it by hand later: an inventory count entered once, straight into the system, the day it is taken; a quote a customer gets online the moment they ask; an intake form that never touches paper.

Most of what we automate is the manual work that's really tech debt: the workaround somebody set up years ago that quietly became the official process. That comes with growing. What should not come with it is your people covering the gap by hand, on the side of the jobs they were hired for.

One telegraph key wired out to three receivers

What are examples of business process automation?

The examples businesses actually ask us for come in three kinds: a process automated and optimized, data collected and examined, and a manual task replaced outright. Each stands on its own; none requires the others.

Process automation and optimization

We take a process your people run by hand and build it into software that runs it the moment it happens, taking out the steps that never earned their place. An order keyed in once that reaches every system that needs it. Our day job. The same goes for counts and work tickets, and when the automation needs your systems connected, we build those connections to your spec.

Data collected and examined

We collect the numbers your business already makes and put them where a decision gets made: the count on a clipboard, the hours on a work ticket, the orders sitting in two systems that have never talked, gathered once and examined in one place. That is the work of getting from the data you collect to the value in it.

Replacement of manual tasks

Some jobs should come off the desk entirely. If people still sign in on paper that somebody retypes later, we swap paper intake for digital forms that write straight into your system, signed on a screen and filed the moment they are finished. And when a customer asks for a price and waits while the one person who knows the formula gets to it, we build an automated quoting system built on your estimator's formula, so the price goes out the moment they ask.

Where do you start?

Put automation around the people who bring in money and the people who make decisions. If a technician's work is what generates an invoice, automate so they are working more than they are pencil whipping. If you sell products, automate getting them in front of customers and out the door. For decision makers, bring the data into one place and measure the business in the ways that matter to them. Then start with the job that waits on one person, or the numbers your people key in twice. That is where the hours and the errors sit, and it is the fastest payback. The tells are easy to spot:

You do not need to arrive with the list. Discovery is part of the work: we sit with the people who run the process, ask the naive questions on purpose, and surface the hidden workaround only one department knows. What we find goes into the scope before anything is built.

How does an automation project work?

An automation project here runs in three steps: discovery with the people who do the work, a build to your spec, and a handover with a feedback loop until the tool fits the job.

  1. Discovery.We sit with the people who do the work and hear the problem in their own words, at the desk where it happens.
  2. The build.We build what you asked for. If we think the spec should change, we say why first, and you decide.
  3. The handover.A first working version goes in front of the people who will use it, and we keep the feedback loop open until it fits the work. No tool nobody uses.

What does automation pay back?

Hours, in more roles than the one you fixed. A count that enters the system the day it is taken gives time back to the person who took it, the manager who checks it, and the accountant who closes the month on it. Speed pays too: how fast a business can put a price in front of a customer and send the invoice behind it drives revenue. And sometimes the saving is the license bill itself, when a custom tool replaces software you pay for per technician.

What does this look like in practice?

In practice, you know an automation works two ways: the people who use it report the job is faster, and the KPIs you track improve. We check both. A first working version goes in front of the people who do the work, and we listen to what they tell us about it. Then the numbers: the measure the job was built to move, whether that is time to quote, hours on the count, or errors chased at month end, should improve. If it has not, the feedback loop stays open.

An old punch card sorting machine, a stack of cards feeding through it into a row of pockets

Common questions about business process automation

Any business where a person keys in something the business already knows. Pentangle does not specialize by industry; we have spent years building for whatever business came in the door, and we will tell you the industrial companies are especially far behind on technology. The industry matters less than the manual work inside it.

Yes. We build the count entered once, straight into the system, the day it is taken; the order that lands in every system that needs it without being retyped; the work order filled in once, from the field, instead of twice at the end of the day.

A first working version goes in front of the people who will use it, then a feedback loop with them until it fits the work. No tool nobody uses. The build runs in the systems you already have, to your spec; if we think something in the spec should change, we say why, and you decide.

Whichever actually fits. We will not custom-build a big system without a strong reason, and if an off-the-shelf tool does the job, we say so. The reason to build runs the other way too. A custom tool in place of a license for every technician? That's the job.

Your tech debt. Our day job.

Bring us the job that waits on one person, or the numbers your people key in twice. We will sit with the people who run it, hear the problem in their words, and tell you plainly what we would build, what we would buy, and what we would leave alone. Start with one job; if it should be bigger, we will say why, and you decide.