Predevelopment Control System
Pre-development,
under control.
The control system for the gap between acquisition and breaking ground — where most development budgets quietly bleed out.
KEEL separates what is confirmed, what is still unverified, what is blocking progress, and what your capital should do next — before the next dollar moves.
Not in active predevelopment? Start with Foundational Access
The Gap
Between closing and breaking ground, most developers are flying blind.
After acquisition, before construction — that window is where projects quietly fall apart. Agency responses go unanswered. Title encumbrances stay buried. Utility connections are assumed, not confirmed in writing. Design advances while permits are still open questions. Capital keeps moving because nobody has a clear picture of what is actually cleared and what is not.
By the time the real constraints surface — a failing septic design, an AHJ access conflict, a floodplain encroachment — you have already spent money you cannot get back on design work that needs to be redone. That is the gap KEEL was built to close.
KEEL governs from the day you identify a target through the day your project is cleared to build.
Every platform assumes execution has already started. Procore. Autodesk. Oracle. None of them own the predevelopment window. KEEL does.
48-Hour Site Assessment
Know exactly where your project stands — in 48 hours.
You send the file. We return a complete picture of what is confirmed, what is still unverified, every open agency item, your top approval blockers, and a clear go/hold recommendation on your next capital move.
You do not need a clean file. Most of the value comes from the mess — unanswered agency responses, title issues nobody has looked at closely, site conditions that have been assumed rather than confirmed. That is exactly what KEEL maps.
Right for your project if you have
- Pre-acquisition — under LOI, in your due diligence window, or approaching close with site questions still open
- Utility uncertainty — well yield, septic capacity, sewer availability, or service connection path not confirmed in writing
- Title or encumbrance complexity — easements, shared access agreements, ROW conflicts, or deed restrictions in the record
- Permit or entitlement blockers — agency responses outstanding, health department approvals pending, AHJ not yet engaged
- Capital decision pending — phased build-out, construction loan commitment, or equity call you need to validate first
- Redevelopment or adaptive reuse — Phase I ESA status, demolition compliance, legacy building conditions, or environmental unknowns
Reviewed within 24 hours. Delivered within 48.
Where projects break down
The work is happening. The control layer is missing.
Requirements pile up
Statutory requirements, agency interpretations, design preferences, and owner wish-list items all land in the same undifferentiated pile. Nobody can say with confidence which items are legally required, which are negotiable, and which are still being treated as requirements when they are actually assumptions.
Open items go cold
Questions get sent to the health department, planning office, or utility provider — and then disappear. No follow-up cadence, no escalation path, no tracking of how long an item has been outstanding. Projects stall not because the answer is no, but because nobody chased the response.
Risk surfaces too late
The septic system that cannot support the proposed use. The fire access geometry that fails AHJ standards. The easement buried in the title commitment that limits your buildable area. These are not new problems — they were in the file from day one. They just were not found until design was complete and money was spent.
How KEEL Works
Eight steps from fragmented file to construction-ready project.
The Real Cost
What unmanaged predevelopment actually looks like.
Not a feature comparison. The specific hours that disappear each week when there is no control system on an active predevelopment project.
Built-In AI
Every agency response, field note, and site visit feeds the project record automatically.
KEEL uses AI to handle the intake work — classifying responses, drafting follow-ups, flagging conflicts with known site conditions, and keeping the project record current without manual re-entry every time something arrives.
Nothing enters the project record without your review. AI handles the intake work. You control what is confirmed.
Full Coverage
Every predevelopment workflow, handled.
Click any row to see how KEEL handles it — from what comes in to what gets recorded.
Field + Spatial Documentation
A site visit becomes a defensible project record — not a camera roll.
Every observation tagged and linked to the approval or open item it addresses. Field photos and spatial data handled as two separate classes of site evidence — both tied to the condition they document.
pressure tank enclosure
width measurement
potential wetlands
east boundary segment
Field photos. FIRM maps. Contour data. All documented. All linked to the open item or approval they affect.
Project Directory
Every project. Every site. One place.
Not a shared drive. Not a task list. A live project environment where every open item, confirmed condition, approval status, and spend decision is attached to the site it governs — from day one.
How the AI works
Six roles. All intake work. You control every decision that matters.
KEEL is not an AI product with a governance wrapper. It is a project control system with AI built into the intake layer — the part that has always been manual, repetitive, and the first thing to fall behind.
The Rule
AI flags. You decide.
Every AI output goes through your review before any condition is confirmed, any approval is cleared, any communication goes out, or any spend decision changes. The system classifies and drafts. Every consequential call is yours to make.
AI handles
Classify · Extract · Draft · Track · Flag · Summarize · Report · Route
You decide
Clear approvals · Authorize spend · Confirm conditions · Send communications · Make go/no-go calls
Platform
One command environment for every project in predevelopment.
Approval status, open items, confirmed site conditions, field documentation, spend decisions, and weekly reporting — all attached to the project they govern.
The control layer that belongs between acquisition and the first construction dollar.
Blocked approvals
Permits, agency confirmations, and site conditions still blocking forward movement.
Open agency items
Questions to health department, planning, utilities, and AHJ — each tracked, owned, and escalated on cadence.
Confirmation status
Confirmed conditions separated from unverified assumptions and outstanding responses.
Risk exposure
Title encumbrances, utility gaps, and environmental flags visible before they become change orders.
Spend recommendation
No additional capital authorized until septic capacity and survey conditions are confirmed.
Next action
Continue agency follow-up and close outstanding confirmations before authorizing additional spend.
Project 001 — Southern Host
A real project, in predevelopment, under control.
Southern Host is not a polished case study. It is an active predevelopment file — 6.07 acres in Baldwin County, Alabama — where site conditions, open agency items, approval blockers, and spend authorization are all visible and tracked in the live project record.
Project status
Live predevelopment. Real constraints. No artificial certainty.
Requirements governed
Site conditions, permit requirements, and utility confirmations structured before design or spend advance.
Approval checkpoints
Each tied to documented confirmation, a responsible party, and a defined consequence if it fails to clear.
Capital at risk
Tracked and visible. No additional spend authorized until site conditions support it.
Start here
Know exactly where your project stands.
Send us the file. We separate what is confirmed from what is still unverified, map every open agency item and approval blocker, identify due diligence gaps, and give you a clear spend recommendation — in 48 hours.