AI Development in Colfax IN for a Town Built on Being Halfway
Property records, public bid paperwork, clerk-office billing and honest timesheets for a town that has held its size for a century and a quarter.
Montgomery Stroud founded this place in 1849 and called it Midway, because that is exactly what it was — the halfway mark between Chicago and Louisville on the Indianapolis, Cincinnati and Lafayette line. It took the name Colfax in 1857, after Schuyler Colfax, the Indiana congressman who went on to be Grant's vice president. The town voted itself incorporated in December 1869 by twenty-four votes to one, and when the Vandalia railroad came through in 1870 and 1871 it grew quickly.
Then it stopped. Colfax hit about 767 people in 1900 and has sat near seven hundred ever since — a hundred and twenty-five years at essentially the same size, in a third of a square mile. That is not decline; it is stability, and it is a genuinely different commercial situation from a town that is emptying or one that is filling up. Nobody here is planning for growth. Everybody here is maintaining something.
Two of those things are on the National Register: the Colfax Carnegie Library and the Rosenberger Building. A town this size holding two listed structures tells you what the local business problem actually is. The buildings are old, the budgets are small, the work is done by contractors who also work in three other counties, and the paperwork attached to all of it — leases, bids, invoices to public bodies, hours for part-time help — is handled by somebody doing it in the evening.
The trading part of Colfax is one street and two corners. The Chatterbox, Rockin' K Boutique, the liquor store and the post office are on Main Street, and so is the Perry Township Fire Department, which is a fair summary of how a small Indiana town divides its labour. The library is round on South Clark Street. Pizza King and the hardware store hold North Oakland; Houze Automotive is on South Columbia; the storage yard is on North Railroad Street, named for what used to run there, and the same railbed is now the Big Four Trail out along East Franklin. The town's water plant is at 208 West Main and the wastewater plant is well out on County Road 700 South. Beyond that it is US 52, I-65 and the farm ground.
Watseka, Illinois·Serving Indiana & Central Illinois·Est. 2024·Founded by a published AI-alignment researcher (thirdwayalignment.com)
In Plain English
What We Fix for Colfax Businesses
Most businesses around Colfax and Perry Township do not call us asking for software. They call because the same thing keeps going wrong every week.
Calls going to voicemail while you work
The phone rings while you are on a job. By the time you call back, they hired someone else. We build systems that answer, capture what the customer needs, and get it to you.
Quotes that take days to go out
Job details end up on a notepad, in your head, and in three text messages. We put them in one place so the estimate goes out the same day.
Customers calling to ask where things stand
Every "just checking in" call interrupts real work. A customer portal lets them see it themselves.
The same information typed in three times
Written on a form, retyped into a spreadsheet, retyped again into the invoice. Enter it once and let it flow.
Maintaining is harder to administer than growing
When nothing is expanding, every job is a repair, every repair is to something old, and every old thing has a history somebody has to reconstruct before work can start. What was done to that Main Street roof in 2011. Which lease says who pays for the furnace. Whether the last bid to the town or the township was approved at the meeting or just discussed. None of it is complicated. All of it is scattered.
Fast, works on a phone, and turns visitors into phone calls and quote requests.
Online quote requests
MAKE MORE MONEY
Customers describe the job and attach photos. You price it accurately the first time.
A customer portal
SAVE TIME
One place for customers to see their job, documents, invoices, and status.
Scheduling
EASIER TO RUN
Jobs, crews, and equipment on one calendar. No double-booking.
Billing and online payment
MAKE MORE MONEY
Invoices go out when the work is done. Customers can pay online.
Customer tracking and follow-up
LOSE FEWER CUSTOMERS
Missed calls get captured. Quotes get followed up on. Nothing depends on remembering.
Document and record management
SAVE TIME
Contracts, photos, signed forms, and certificates found in seconds instead of folders.
Custom software built around your business
EASIER TO RUN
When your process has outgrown spreadsheets, paper, or software built for somebody else.
What about AI?
AI is one tool we can put inside your system. We use it when it saves you time, organizes information, finds something faster, or prepares work for your review.
If ordinary software can do the job better, we use ordinary software instead.
We are not here to sell you AI. We are here to build the thing that fixes the problem.
Your business does not have to change to fit our software. We build the software to fit your business.
We do not hand you another piece of software and expect you to figure out how to use it.
01We learn how your business actually works — a real week, not the version on paper.
02We find where the most is being lost — usually one specific handoff.
03We build the smallest thing that fixes it — one workflow, fixed price, a result you can see.
04We add to it as you grow — each piece connects to the last.
A person on your team can always review anything important before it goes out. We are a Indiana-based team and we work under an NDA whenever you want one.
Four workflows built around Colfax and Perry Township.
For owners and IT folks who want the specifics. Each one starts at the surface a customer or a crew actually touches, automates the repeatable middle, keeps a person on the gate that matters, and ends in something you can hand to an auditor, a customer, or a regulator.
Research focus: a town that has held the same population for a hundred and twenty-five years, where the commercial activity is maintenance rather than growth: old buildings, public-sector work, a small municipal office and employers with a handful of part-time people.
01 / Storefronts that are older than the paperwork
Step 1 · Where it starts
Each unit has a page holding the lease, the tenant, the insurance certificate, the renewal date and the repair history, reachable from a phone standing in the doorway.
Step 2 · What gets automated
Scanned leases and certificates are read for the dates and obligations that matter — who covers what, when it renews, what the cover limit is — and filed against the unit instead of the year.
Step 3 · The process it plugs into
A repair request logs against the building and the tenant together, so the argument about who pays for it starts from the lease clause rather than from two different memories of a handshake.
Step 4 · SolaceSentry review
You confirm every obligation the system extracts before it is relied on. A machine reading of a 1970s lease is a prompt to go and check, never an answer.
Step 5 · What leaves the system
A property file that answers a question in a minute, and renewals and lapsed certificates that surface before a tenant or an adjuster raises them.
Proof metric: Insurance certificates or leases found expired after the fact, and hours spent assembling a history for one building.
02 / Bidding to bodies that meet once a month
Step 1 · Where it starts
A bid is assembled from a template that already knows your licence numbers, your bond, your insurance and your standard exclusions, so the only new writing is the scope.
Step 2 · What gets automated
Specifications and invitations to bid are read and reduced to a checklist of what must be submitted and by when, with the requirements you have missed before highlighted first.
Step 3 · The process it plugs into
Submitted bids, meeting dates, approvals and change orders sit on one line, so you know whether a job is live or still waiting on a board that meets on the second Tuesday.
Step 4 · SolaceSentry review
You approve every price and every submission. Nothing is filed to a public body without a named person on your side reading it in full.
Step 5 · What leaves the system
Bids that arrive complete the first time, and invoices to public bodies that are not returned for a missing certificate.
Proof metric: Bids rejected or returned for a paperwork defect, and days from work completed to payment received.
03 / The town office on a Sunday night
Step 1 · Where it starts
Residents can read a bill, pay it, report a problem or find out when the board next meets without waiting for a weekday morning and a phone that rings in an empty room.
Step 2 · What gets automated
Reported problems are sorted into the right category and the right department, and duplicate reports of the same broken thing are grouped rather than each generating its own trip.
Step 3 · The process it plugs into
Billing, service reports, ordinances and the meeting record live in one place with a clear line between the official version and the plain-English explanation of it.
Step 4 · SolaceSentry review
A clerk or board member releases everything that carries the town's name. The official record is edited by people, on the record, and the system never speaks for the board.
Step 5 · What leaves the system
Fewer calls asking questions a page could have answered, and a public record that can be found by somebody who does not know the right word for it.
Proof metric: Share of bills paid without a phone call, and duplicate reports of the same issue.
04 / Hours for people who work three days a week
Step 1 · Where it starts
Time is recorded where the work is, by the person doing it, in a few seconds — no fob, no terminal on a wall, no laptop in a truck.
Step 2 · What gets automated
Entries that look wrong — a shift with no end, an overlap, an impossible drive between two jobs — are flagged the same day rather than found by a bookkeeper a fortnight later.
Step 3 · The process it plugs into
Hours attach to the job as well as the week, so a job that ran over is visible while it is running and not only when the invoice does not cover the wages.
Step 4 · SolaceSentry review
Somebody approves every timesheet before it reaches payroll, and any correction keeps the original alongside it rather than replacing it.
Step 5 · What leaves the system
Payroll that runs without a Sunday evening of reconstruction, and job costs that include the labour that actually went in.
Proof metric: Timesheet corrections made after payroll ran, and jobs whose recorded hours exceed what was quoted.
Payment Plans
Premium custom work without one painful check.
We are not trying to be the cheapest software on the shelf. We are trying to be the lower-risk custom path when cheap apps do not fit and enterprise platforms are too much. Approved setup can be split across the build while monthly support stays predictable.
The goal is simple: price above basic SaaS because the work is custom, but package the first step so the monthly decision feels closer to a serious software subscription than a traditional open-ended agency project.
2026 Appreciation Discounts
2026 USA 250 Birthday Special
10% off eligible DID service fees
Available for new approved projects and support agreements signed by December 31, 2026.
Veteran and disability-owned businesses
Additional 5% off eligible DID service fees
Veteran-owned and disability-owned businesses can stack this with the USA 250 special.
Discounts may stack up to 15% off eligible DID service fees. Hosting, software licenses, SMS, AI usage, taxes, data licenses, and other pass-through vendor costs stay separate.
We are not trying to beat every cheap subscription. We are trying to beat the total cost of forcing a local business into software that does not match how it works.
Not the cheapest app
A generic monthly tool can be cheaper when your process already fits it. We say that plainly.
Less than a full custom build
Most custom software projects start far above these entry offers. We narrow the first scope so a local buyer can start.
Premium because it fits
The value is the mapping, setup, integration, review controls, and local support around the way the work really happens.
Custom Bridge Plans
Starter Bridge
$750 activation + $399/mo
A narrow custom workflow that feels closer to SaaS: contractor follow-up, a training tracker, a simple evidence vault, or one intake flow.
Growth Bridge
$1,500 activation + $699/mo
Best for teams that need several workflow steps, light integrations, a dashboard, a portal, or staff-facing automation.
Regulated Bridge
$3,000 activation + $1,250/mo
For legal, healthcare, cyber, manufacturing, and audit-sensitive work where access controls, review steps, and evidence matter.
Bridge plans assume a 36-month support agreement. If the agreement ends early, the unpaid setup balance becomes due. Third-party software, hosting, SMS, and AI usage stay separate.
Market Price Check
Basic subscriptions
Often about $30-$550/month before extra users, add-ons, setup time, and process gaps.
Best when a business needs its calls, quotes, files, evidence, approvals, and follow-up connected around the way it already works.
Custom agencies
Public software-project guides commonly place small custom builds in the $10k-$50k+ range, with U.S. senior work often $120-$250+/hr.
DID uses fixed entry offers and smaller first scopes so a local team can prove the workflow before approving a larger build.
Enterprise platforms
QMS, field-service, SOC 2, GRC, and vCISO paths can quickly reach the low tens of thousands once onboarding and support are included.
DID is the bridge: more tailored than a cheap app, far less commitment than buying enterprise software before the team is ready.
Entry audit credit
For many local buyers, a workflow audit can be credited toward the first build when the implementation is approved within 30 days.
Setup split
Approved setup can be billed by milestone or spread over 3-12 months depending on region, scope, risk, and monthly support.
3-year partner price
A 36-month support agreement can earn a 10-12% managed-support discount, price-lock normal support rates, and reduce upfront strain.
A stable town of about seven hundred in a third of a square mile, with two National Register buildings, a public library on South Clark Street, a Perry Township fire department on Main Street, a small municipal office, and businesses whose work is maintenance rather than expansion.
Making history findable. The recurring cost here is not doing the work, it is reconstructing what was done last time — to that building, on that bid, by that part-time employee — before the work can start.
Where most people start
A single fixed build for a contractor, a property owner or the town office. Growth Bridge only where several of those sit in the same hands.
Anything touching public money, employee hours or a tenant's insurance goes to the stricter tier with logging, because each of them is a record somebody can compel you to produce.
When you do not need us
There are perfectly good cheap products for time tracking and for basic property management. If one of them fits how you already work, that is what you should buy, and we will say so without invoicing you for the opinion.
We fit where the records are old, mixed and paper-born — a lease from before the current owner, a repair somebody remembers, a bid document written to a specification nobody has read twice — and something has to make them searchable.
What we would take on first here
Lease, certificate and repair history held per unit in older commercial buildings
Bid assembly and public-body invoicing that survives a monthly meeting cycle
Municipal billing, issue reporting and public records for a small town office
Job-linked time recording and approval for part-time crews
Questions from Colfax owners
Straight answers about working with us here
The town has been the same size since 1900. Why would anything need to change?
Nothing about the town needs to change. What has changed is who is willing to wait. A tenant, a bidder or a resident who cannot find an answer in a minute now assumes there is not one, and small organisations lose credibility that way without ever hearing a complaint. Stability is an argument for cheap durable systems, not for none.
Our leases go back decades and half of them are typed on paper. Where does that even start?
With a scanner and low expectations, honestly. We read what we can, pull out the dates and the obligations, and hand you a list of what the machine could not make sense of — which is the useful output, because it tells you exactly which documents need a human hour. Nobody retypes forty leases, and nobody pretends the extraction was perfect either.
We bid to the town, to Perry Township and to the library. Is that enough public work to bother?
It is if you are losing bids to missing paperwork rather than to price, which is common and infuriating. The build here is small: your licences, bond and certificates held once, a checklist read off each invitation, and a line showing whether a job is approved or still sitting until the board next meets. That is weeks of work, not months.
What does this cost for an operation with four people and no IT budget?
One fixed price for one finished thing, paid on delivery, with no monthly seat charge running in the background whether anybody logs in or not. We would rather build you one small system you own outright than sign you to a subscription that quietly becomes the fourth-largest line on your accounts.
If the board changes or the owner sells, does everything walk out the door?
No, and that is the point of insisting the accounts are in the organisation's name rather than an individual's from day one. Leases, service histories, meeting records and billing all export in ordinary formats whenever asked. A town of seven hundred has seen enough records disappear with a retiring clerk to justify making that a written term rather than a promise.
Would you build the official ordinance record itself?
We will host and organise it, and we will not touch what it says. The distinction we hold to is that the legal text is the board's and is edited by people the board authorises, while the plain-English page explaining what it means for a resident is separate and clearly labelled as such. Blurring those two is how small towns end up in arguments they cannot win.
Where is the AI in this, honestly? Most of it sounds like a database.
Most of it is a database, and we would rather say that than dress it up. The genuine machine-learning work is narrow: reading an old lease, reducing a bid specification to a checklist, spotting a timesheet entry that cannot be right. Those three things save real hours. The rest is careful, ordinary software, priced as ordinary software.
How would we know after six months whether it was worth the money?
Because we pick the number before we start and put it where you see it. Bids returned for a defect. Hours spent building one building's history. Bills paid without a phone call. If that figure has not moved by spring, the build failed, and we would rather have that conversation with a number on the table than let it fade out quietly.
Start with the one handoff that costs you the most. We scope it for a fixed price, build it, and show you it works before anyone talks about a bigger system.