Princes Lakes IN AI Development for Lake Associations and Boards
Fourteen private lakes, each with its own rules, dues, dam and volunteer board, inside a town of twelve hundred people.
Princes Lakes incorporated in 1956 and took its name from four lakes that each had "Prince's" in the title. What it is now is a square and a half of ground with fourteen lakes on it, and here is the part outsiders always get wrong: those lakes are privately owned and, as the town itself puts it, not freely open to the public. There is no marina, no boat ramp for visitors, and no state property. North, White, East, Hants, Riley, Carolyn, Jefferson, Brown, Latimore, Donald, I and H are among the names, and each is somebody's responsibility.
The responsibility takes two legal shapes. A lake conservancy is a governmental body with real authority, taking in every property owner in its district and managing its own finances. A Lake Lot Owners' Association is a private organisation doing much the same job without that authority. Either way, the same organisation handles access, enforces rules, oversees a dam, and answers to IDEM and the Army Corps of Engineers. In a town of twelve hundred, that structure repeats a dozen times over.
The people carrying it are volunteers, usually retired — the median age here is 49.4, well above the county — and they are running what amounts to a small utility and a small government in their spare time. Meanwhile nearly a quarter of the housing units sit empty at any given time, which means seasonal owners, caretakers with keys, docks that come out in October, and a whole trade built around houses whose owners are somewhere else.
The rest of the town takes one paragraph to describe, and we would rather write the short honest one than a long invented one. This is Nineveh Township; the children go to the Nineveh-Hensley-Jackson United schools at Indian Creek; Eddie's Lakeview Pizza is the restaurant. Search the public datasets for businesses inside the town line and you get two results, one of them a chain, and not a single regulated site. There is no main street here, no industrial ground and no commercial register to speak of, because the thing this place is made of is water, houses around water, and the organisations that own the water.
Watseka, Illinois·Serving Indiana & Central Illinois·Est. 2024·Founded by a published AI-alignment researcher (thirdwayalignment.com)
In Plain English
What We Fix for Princes Lakes Businesses
Most businesses around Princes Lakes and Nineveh 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.
A volunteer inherits a shoebox and a spreadsheet
Every few years the treasurer or the secretary of a lake organisation changes. What gets handed over is a spreadsheet with somebody else formulas in it, a folder of scanned letters, and a great deal of knowledge that stays in the old volunteer head. The dam inspection report from four years ago is somewhere. Who paid their assessment in 2021 is somewhere else. That handover, repeated across fourteen lakes, is the biggest single risk in this town.
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 Princes Lakes and Nineveh 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 of twelve hundred containing fourteen privately owned lakes, each governed by a conservancy district or a lot owners association with dam responsibility and environmental compliance behind it, and a housing stock that is nearly a quarter seasonal.
01 / Dues, assessments and who has actually paid
Step 1 · Where it starts
A member page where a lot owner can see their own balance, pay it, and update the address the notices go to — because a good share of the owners here do not live at the lake.
Step 2 · What gets automated
Payments arriving by cheque, transfer and card are matched back to lots rather than to names, which is what stops a property that changed hands in March becoming an unexplained arrears line in September.
Step 3 · The process it plugs into
Assessments are raised against the lot, so ownership changes carry the record forward and a new owner inherits a clear position rather than an argument.
Step 4 · SolaceSentry review
The treasurer approves every write-off, late fee and payment plan. Nothing that affects what a neighbour owes happens without a board member behind it.
Step 5 · What leaves the system
A reconciled ledger a board can present at a meeting, and notices that reach the right address the first time.
Proof metric: Assessments outstanding at year end, and hours the treasurer spends reconciling before each meeting.
02 / Dam files, inspections and the agencies above you
Step 1 · Where it starts
A private area holding the engineering reports, inspection records, permits and correspondence for a structure, each with a date and a named responsible person.
Step 2 · What gets automated
Reports and permit letters are read for the dates and required actions inside them, so a recommendation with a deadline becomes a tracked item rather than a paragraph on page nine.
Step 3 · The process it plugs into
Required actions, inspection intervals and agency correspondence sit on one schedule, so a board can see what is due next year rather than discovering it in a letter.
Step 4 · SolaceSentry review
A named officer confirms every submission to IDEM or the Corps. No regulatory correspondence is generated or sent by a system on a board behalf.
Step 5 · What leaves the system
A complete, ordered file for each structure that survives a change of officers, and deadlines met without a scramble.
Proof metric: Required actions closed before their due date, and how long it takes a new officer to find any given record.
03 / Rules, access and the boat on the wrong lake
Step 1 · Where it starts
A page per lake stating plainly who may use it, what the rules are, how guests work, and what a sticker or permit means — so the answer is published rather than explained by a volunteer at a dock.
Step 2 · What gets automated
Complaints and reports are grouped by lake and by issue, so a recurring problem at one shoreline is visible as a pattern instead of as six unrelated emails across a summer.
Step 3 · The process it plugs into
Permits, guest passes and rule notices are recorded against the lot, giving a board a consistent history instead of a memory of who was spoken to last year.
Step 4 · SolaceSentry review
Enforcement is a board decision, always, and every notice is signed by a person. We do not build systems that issue sanctions to neighbours automatically.
Step 5 · What leaves the system
Published rules people can read for themselves, and an enforcement record that is even-handed because it is written down.
Proof metric: Repeat questions the board has to answer individually, and complaints closed with a recorded outcome.
04 / Looking after a house whose owner is elsewhere
Step 1 · Where it starts
A booking and reporting page for caretakers, dock services and trades, where an absent owner can request work and see photographs of what was done.
Step 2 · What gets automated
Requests and photographs are sorted by whether the property is currently occupied and whether the issue can wait for the season, which is the judgement that orders a caretaker week.
Step 3 · The process it plugs into
Each property carries its own file — keys held, water shut-off, dock in or out, what was done last autumn — so seasonal open and close is a checklist rather than a memory.
Step 4 · SolaceSentry review
Work above an agreed value is authorised by the owner before it starts. Nothing is committed on an absent owner behalf.
Step 5 · What leaves the system
Seasonal open and close done in a consistent order with a photographic record, and owners who can see what happened without driving down.
Proof metric: Properties closed for winter before the first freeze, and callbacks caused by something missed at close.
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 Nineveh Township town of twelve hundred containing fourteen privately governed lakes, with an older resident population, a heavily seasonal housing stock, no commercial district at all, and more volunteer-run organisations per head than anywhere else in the county.
The buyers here are boards and one-person service businesses. Both need the record to survive the person, because in this town the person always changes eventually.
Where most people start
One small, finished build. Boards should not be signing up to programmes of work and we will not propose one.
Conservancy district records and anything touching a dam move to the tighter tier, because a conservancy is a governmental body and a dam file is read back by a regulator.
When you do not need us
Homeowner association platforms and accounting packages exist and often fit a lake organisation adequately. Where one does, we will name it and tell you to buy it instead of hiring us.
We fit where those products have no concept of a dam file, a conservancy district assessment, or a lot that has changed hands twice since the last notice went out.
What we would take on first here
Assessment and dues records held against the lot rather than the owner, so ownership changes do not break them
Dam and compliance files with tracked required actions that survive a change of officers
Published per-lake rules and a consistent, recorded enforcement history
Seasonal open and close records for caretakers working properties whose owners live elsewhere
Questions from Princes Lakes owners
Straight answers about working with us here
People assume this is a public lake town. Why does the distinction matter to a project?
Because it changes who the customer is. A public reservoir town sells to visitors — marinas, launch fees, rentals. Here the lakes are privately held and not open to the public, so there is no visitor economy to build for. Nor is there much of any other kind: the public datasets return two mapped businesses inside the town line, Eddie's Lakeview Pizza and a chain outlet, and no regulated sites at all. That is worth saying out loud rather than dressing up. The organisations that actually need systems here are the associations and conservancies that own the water, and the trades that look after the houses around it. Getting that wrong would produce a page, and a project, aimed at nobody.
Our board is five retired volunteers. Are we the sort of client you take?
Yes, and we scope for that reality rather than pretending it away. It means the system has to be usable by someone who did not choose to be treasurer and will hand it on in three years. Fewer features, obvious labels, and a written handover as part of the deliverable. A clever system that only the current secretary understands is a liability dressed up as an asset.
A conservancy district is a governmental body. Does that change the rules for us?
It does, and it is worth saying out loud early. A conservancy has authority a private association does not, which brings public record obligations and a higher standard for how decisions are documented. Practically that means approval steps and an audit trail are built in from the start rather than added if someone asks. A private lot owners association can be looser, and we will tell you which set of rules you are actually under.
Every officer change loses records. Can that actually be fixed?
It is the single most fixable problem in this town, and the reason we would take a project here at all. The fix is not clever software. It is putting the ledger, the dam file, the rules and the correspondence somewhere that belongs to the organisation rather than to a person, in formats that open in ordinary programs, with a written note of where everything is. Half the value lands the day the current officer stops being the only route to anything.
What would this cost an organisation that collects assessments from ninety lots?
Less than most boards expect, because the honest scope is small. We size the first build so it can come out of an ordinary annual budget without a special assessment, and we say the number in writing after one mapping session rather than billing by the hour. If it cannot be done at that size we say so and suggest what to do instead, which is sometimes just a shared drive organised properly.
Does any of this need artificial intelligence, or are we being sold a fashion?
Mostly you are not, and we would rather say that than take the fashionable version of the money. Matching cheques to lots is arithmetic. A ledger is a ledger. The one place a machine genuinely helps is reading a long engineering or inspection report and pulling out the dated actions buried in it, which volunteers routinely miss. Everything else here is ordinary software done carefully, priced accordingly.
Whose information is it once it is in a system, and who can see it?
The organisation owns it, not us and not the current officers personally. Owner contact details and payment history are visible only to the board roles that need them, every export is logged, and the whole set comes out in a plain file whenever the board votes to take it. We are a US-based team and we will sign whatever confidentiality terms your board wants before we see a single lot record.
Could several of the lakes share one system, or does each need its own?
Sharing is usually the better answer and it is rarely the first instinct, because these organisations are used to being separate. A shared build with each lake keeping its own records and its own board control costs a fraction of fourteen separate ones and makes handover easier everywhere. Whether it is politically possible is a question for the boards, not for us, but the technical side is straightforward and we will price both ways.
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.