Separate properties. Stated relationships. One boundary.
Collaborative Concept is connected to brands, products, and sites that are not corporate service lines. This page is the policy that governs them: what each one is, what role it plays, how this site treats it, and where the line sits.
Ventures carry real value, and none of it survives if a visitor cannot tell a venture from a service line. So every related property is assigned one corporate role first, and the role determines how much of it belongs on this site.
A corporate role answers one question: what is this property to Collaborative Concept? The site treatment answers the next one: how much of it belongs on the corporate site, and in what form. Settling the first question makes the second mechanical rather than a matter of taste.
Nothing on the list below is a service you buy from Collaborative Concept. A venture runs under its own brand, on its own site, for its own audience. What appears here is a description of the relationship and, where the policy allows it, one case study — never a second set of service pages competing with the two divisions.
That is also why the link to this page sits in the footer rather than in the primary navigation. Placing ventures beside Development and Solutions would suggest they are a third thing the firm sells. They are not, and the navigation should not have to be explained.
The treatments are deliberately narrow: an independent site stays independent, a case study stays a single case study, and a selected-work entry stays one entry. Each is a ceiling, not a starting point.
The policy
Property
Corporate role
Site treatment
Florida Solar Exit
Focused Solutions venture
Independent brand and site; one concise venture case study on the corporate site.
Palm Beach Wake Boats
Venture
Independent brand and site; removed from primary corporate navigation.
Adometr
Venture / product
Independent brand and site; presented as selected work only.
K5 and partner properties
Partner / development proof
Ownership and the partner relationship clearly identified.
Specialized compliance sites
Solutions deployment
Used as a case study; the market-specific conversion site kept separate.
A property that does not fit a row on this table is not listed until it does. The table is the page: the entries below restate it in sentences, and the boundary section states what none of them claim.
The Properties
Each property, and the relationship behind it.
Each entry says what the property is and how it relates to the firm. No outcome, transaction, acquisition, or result is described for any of them.
Solutions
Florida Solar Exit
A separately branded venture on the Solutions side of the business, run under its own name and its own site rather than as a Collaborative Concept service line. Its subject is Florida solar financing agreements and the paperwork behind them.
Relationship. A venture the firm is involved in, disclosed here rather than implied by placement. Boundary. The corporate treatment is one concise venture case study and nothing beyond it. Nothing here is legal, tax, or financial advice, and no result is described for the venture or for anyone who works with it.
A venture that operates under its own brand and its own site, speaking to its own market. It is not a Collaborative Concept service line and is not marketed as one.
Relationship. An independent brand the firm is involved in; the involvement is stated here rather than signalled by where the link appears. Boundary. Under this policy it is removed from the primary navigation of the corporate site, and it is not bundled into, sold through, or referred as part of a client engagement.
A venture product maintained under its own brand and its own site, on its own roadmap. It sits outside the two divisions rather than inside either one.
Relationship. A venture product the firm is involved in, identified as such wherever it appears. Boundary. The corporate treatment is a selected-work entry only — not a product line, not a deliverable inside a Solutions engagement, and not something a client engagement includes by default.
Properties involving partners rather than Collaborative Concept alone. Where one of them appears on this site, it appears as development proof — an illustration of how the work is approached, not a portfolio claim.
Relationship. Each entry identifies who owns the property and what the partner relationship is; listing one here is not a claim of sole ownership or control. Boundary. Any transaction sits with the parties to it, and design, construction, brokerage, and legal work are performed by the appropriately licensed professionals engaged for that scope.
Market-specific sites classified as Solutions deployments rather than as ventures. Each is scoped to a defined market and keeps its own audience and its own calls to action, separate from the corporate site.
Relationship. A Solutions deployment rather than a venture the firm brands as its own; the corporate site describes the build, not the market it serves. Boundary. The deployment is treated as a case study and the market-specific site stays separate. Where Collaborative Concept builds or operates such a site, it does not perform the regulated or licensed work behind the subject matter.
Four steps, in the same order every time. The site only changes at the last one.
Name the Property
Identify the site or business exactly as it is branded, without folding it into a service line.
Assign the Role
Give it one corporate role: venture, venture product, partner proof, or Solutions deployment.
Set the Treatment
The role decides the ceiling: independent site, one case study, one selected-work entry, or a footer link.
State the Boundary
Write the relationship and any licensing, transaction, or referral limit into the entry itself.
A role can change. When it does, the status label and the treatment change with it — the surrounding copy is not rewritten to suggest more than the label says.
Boundary
Where ventures end and client work begins.
Ventures are operated separately from client engagements. That separation is the reason this page can exist at all.
A client engagement is scoped, priced, staffed, and measured on its own terms. A venture does not ride along inside it, is never a condition of working with the firm, and is not billed through it. Where a venture and an engagement could touch the same matter, the overlap is disclosed in writing before work begins and the client decides how to proceed.
Naming a property on this page describes a relationship, not a title. Ownership, partner interests, and transaction roles sit with the parties to them and are identified inside the entry rather than assumed from the fact that it is listed.
The same limits that govern the rest of the site govern this one. Collaborative Concept leads strategy, coordination, and oversight; it does not perform licensed work, and a venture does not create an exception to that.
Venture disclosure. Ventures are operated separately from Collaborative Concept client engagements. A venture is not a client service, is not staffed or billed through an engagement, and is never a condition of working with the firm.
Naming a venture or partner property on this page is not a claim of sole ownership, control, or a licensed role in it. Licensing, transaction, and referral boundaries are stated in each entry, and licensed work is performed by appropriately licensed professionals engaged for that scope.
What every entry states
Property
The site or business, named as it is branded.
Corporate role
One role from the policy table, carried as the status label.
Site treatment
The ceiling on how much of it appears on this site.
Relationship
What the property is to Collaborative Concept, in plain terms.
Boundary
The licensing, transaction, or referral limit that applies.
What no entry states
No revenue, savings, recovery, or performance figure. No acquisition, wind-down, exit, or transaction. No claim of sole ownership, and no licensed role the firm does not hold. Where a number or an outcome would belong, it stays off the page until it has been verified and approved for publication.
Image slot
Related
Where this sits next to the two divisions.
Ventures are organized apart from client work, but they draw on the same two disciplines. Both divisions, and the proof library that serves them, are documented in their own sections.
