Custom business software / Tampa, Florida

Software for the work that outgrew the spreadsheet.

Fintlock builds the internal tools a company runs on: quoting, spec checking, reporting, document generation, and the connections between systems that people are still bridging by hand.

The problem

The problem is usually a process, not a program

It starts as a spreadsheet someone clever built. Then a second one. Then a shared folder of them, a few macros nobody dares touch, and a person who is the only one who knows how it all fits together. Orders get retyped from one system into another. Someone checks specifications against a catalogue line by line. Reports take a day to assemble because the numbers live in three places.

Off-the-shelf software rarely fixes this, because the process it is meant to support is specific to your company. What fixes it is a small, purpose-built tool that does exactly that job, on the hardware you already have, and is simple enough to hand to a new hire.

What we build

What we build

We build desktop programs for Windows and Mac, browser-based internal tools, and integrations, depending on where the work happens. Typical projects:

  • Quoting and estimating tools that pull prices and rules from your own data
  • Specification checking against product catalogues, manufacturer data, and job requirements
  • Document generation: proposals, submittals, reports, and certificates from one set of inputs
  • Reporting that gathers accounting, sales, and operations figures into one screen
  • Integrations between the systems you already pay for, so nothing is retyped
  • Replacing a critical spreadsheet with something several people can use at once without breaking it

Project example / Building materials

Checking specifications without the line-by-line.

A building materials supplier was checking product specifications by hand: someone would open the job requirements, the product data, and the order, and compare them line by line. It was slow, it depended on a few experienced people, and a miss was expensive.

We built a spec-check tool around the way that work was already done. It takes the requirements and the products in question, flags what does not match, and produces a record the team can send on. The people who did the checking by hand were in the room for every review, which is why it fit on the first day.

We keep client work private, so this is described in general terms. We are happy to walk through it in a conversation.

Type
Internal tool
Industry
Building materials
Status
In daily use
Spec checkIllustration, not client data
RequirementProduct dataMatch
R-value 19, unfacedR-19 unfaced batt, 15 inMatches
Fire rating: Class AClass A (ASTM E84)Matches
Width: 16 in on center15 in battCheck
Thickness: 6.25 in6.25 inMatches
1 item to checkExport record

How a project runs

Three stages, each with something to show for it.

A written scope and a price before work starts, working builds while we build, and a proper handover when it ships. More on how we work.

1

Scope

We start with a conversation about what happens today and what needs to change. From that you get a written scope and a price before any code is written.

You getA written scope and a fixed price
2

Build

Design and development run in short cycles. You review working software as it comes together, on your own phone or desk, rather than a slide deck about it.

You getWorking builds to review along the way
3

Launch

App Store submission, deployment, documentation, and a proper handover. When it ships, your team can run it, and we are still reachable when something needs attention.

You getA shipped product and the keys to it

Questions

Things people ask about business software.

Desktop program or browser tool: which do we need?

If the work happens at a few fixed desks with local files, a Windows or Mac program is often simpler and faster. If several people in different places need it, or it has to run on phones, we build it for the browser. We will recommend one after seeing the process.

Will it work with the software we already use?

Usually, yes. Most modern systems, from accounting to CRM to supplier portals, have a way to read and write data. Connecting them is a large part of what we do.

What happens when we need a change later?

The code is yours and documented. We can stay on for updates, or hand it to your own people. Either way, a small tool built for one process is much easier to change than a big platform.

Do you work outside construction and building materials?

Yes. That is where we have the most depth, but the same approach applies to any company with a process that has outgrown its spreadsheet.

Contact

Tell us what needs to work better.

A few sentences about the problem, who deals with it, and what you would like to change is enough to start. We reply within one business day.

Start a project Tampa, Florida. Working with clients across the US.