CBKDI
Conor Keilty / CBK Development Intelligence

I design the systems, processes, and tools that operators actually run on.

Fifteen years in real‑estate development: five on the GC side, ten sponsor‑side. Field through investment committee.

For developers, builders, designers, and operators who need optimized workflows and clearer decision tools.

01 The work Where I focus

What the work usually looks like.

01 · Company

The system that runs across every project.

Standing up a development function from scratch, or restructuring how an existing operation runs. I help define the process, the roles, the sequence, and the handoffs, and leave a written playbook you can hand to the next hire.

Typical artifacts
  • Development playbook
  • RACI / handoff map
  • Change-order & billing workflow
02 · Project

The proforma that needs to survive contact with the site.

I sit with the model, the drawings, the term sheet, the entitlement calendar, and the capital stack, and tell you what breaks first.

Typical artifacts
  • Proforma audit
  • Entitlement & capital timeline
  • IC scenario package
03 · Problem

A bounded problem on a short fuse.

A review, a one-off tool, a workflow map. I take it on, deliver, and don't linger.

Typical artifacts
  • Risk memo
  • Cost-tracking dashboard
  • One-off workflow or tool
02 About The short version, first person

Most of the hardest problems on a project turn out to be systems problems.

I'm Conor Keilty: a licensed architect with fifteen years across design, GC execution, sponsor-side development, and investment committee decisions. Five years in the field, ten years in the model and the deal.

What I've found, across every chair I've sat in, is that the hardest problems on any project aren't the obvious problems. They're the systems problems. The drawings say one thing, the field says another, the proforma says a third, and somebody has to sit in the middle and decide what is real.

03 Engagement How the work gets scoped

Three ways an engagement usually runs.

Every engagement starts with a conversation. We'll talk through the project, the decision you're trying to make, and whether it fits my lane. If there's a fit, the work usually takes one of three forms.

A · Retainer

Ongoing development intelligence for decisions that compound week to week.

Standing access to senior judgment on the calls that don't fit a fixed-scope artifact: weekly meeting, in the model, in the room when the answer matters.

Typical
Monthly, renewable.
Pricing
Monthly retainer, capped hours.
Output
Judgment in the room; artifacts along the way.
B · Fixed scope

A named deliverable, on a calendar.

We name the artifact, agree on what 'done' looks like, and I deliver it inside an agreed window.

Typical
4 to 12 weeks.
Pricing
Fixed fee, scoped up front.
Output
A thing. And the writeup to run it.
C · Hourly

A specific problem, on the clock.

A bounded problem on a short fuse: a review, a day in the model, a week mapping a workflow.

Typical
2 to 6 weeks.
Pricing
Hourly, against a project minimum.
Output
Direct time; same artifacts as the other two.
04 Contact The start of the conversation

Tell me the shape of the problem.

Not sure what you need yet? That's fine. Send the messy version: the model, the schedule, the open questions, or just a short note. We'll start with a conversation and figure out whether I can help.

Form goes to my inbox. I read every one and reply inside two business days.

Based Pacific Northwest. Pacific Time.
Start a conversation
Plain language. No NDA needed for a first note.