Insights
Practical thinking for development and business operations.
Two editorial tracks, written from method — how a decision gets tested, what gets checked first, and where a plan usually bends.
The Index
Articles
Each piece sits in one of two tracks. Filter by track, or read straight through. Pieces are added to a track as they are written.
Development
Navigating Non-Conforming Lots in Coastal Communities
How a constrained or legacy parcel gets read before anything is drawn — what the survey and public record actually say, what governs the lot today, and where a plan has to bend to fit.
Read Article
Solutions
From Disconnected Tools to Operational Clarity
What happens in a business running on tools that never spoke to each other — mapping the process first, deciding what the software is actually for, and giving each step an owner.
Solutions TrackEditorial Tracks
Two tracks, the same two lines of work
Insights follows the structure of the firm. One track covers property — how an opportunity is tested before it is pursued. The other covers operations — how work actually moves through a business. Both are written about method, not outcomes.
Development
Development Insights
Property-side thinking: how a site is read, how a plan is validated, and how the sequence of approvals shapes what can be built.
- Reading a parcel — survey, plat, and public record
- Non-conforming and legacy lot conditions
- Entitlement paths and the public process
- Feasibility work and the assumptions worth stress-testing
- Coastal and floodplain considerations
- Sequencing design, permitting, and construction
Solutions
Solutions Insights
Operating-side thinking: how work moves between people, what has to be true before software is worth buying, and how a system stays used after launch.
- Mapping a process before choosing a tool
- Lead follow-up and pipeline hygiene
- Who owns the CRM, and what ownership means day to day
- Document, estimate, and permitting workflow
- Handoffs between field, office, and customer
- Reporting people will actually read
Editorial Standard
How we decide what goes here
An article earns a place here when it describes something we would otherwise have to explain twice — a sequence, a constraint, or a decision that keeps recurring.
Every piece is written to be useful on its own. It describes the work in the order the work happens, names the checks that come before commitment, and is explicit about what still has to be confirmed by someone licensed to confirm it.
What you will find
- Plain description of how a decision gets made, in sequence
- The verification steps that come before commitment
- The constraints that shape a plan, and who governs them
- The questions worth asking before money or time is spent
What you will not find
- Client names, or project details we do not have permission to publish
- Performance figures, savings claims, or before-and-after numbers
- Vendor rankings, sponsored placement, or affiliate links
- Legal, engineering, appraisal, or design determinations
General information only. Articles here describe process and method. Collaborative Concept is not an architect, engineer, contractor, broker, attorney, appraiser, or inspector, and nothing published here is legal, engineering, design, or financial advice.
Requirements differ by jurisdiction and change over time. Confirm anything that affects a decision with the licensed professional for that discipline and with the authority having jurisdiction.
Keep Reading
Where this connects
Development
Find the opportunity. Prove the plan. Execute with discipline.
The property side of the practice, and the process behind the Development track.
Explore DevelopmentSolutions
Recover revenue. Fix the process. Build the system.
The operating side of the practice, and the process behind the Solutions track.
Explore SolutionsProof in Practice
Development opportunities and business solutions, clearly organized.
Selected Work, where the methods described in these articles are applied.
View Selected Work