Software proposal High-level proposal for Corland Partners
Prepared for Corland Partners
June 2026

Unified software for Corland's operating portfolio.

This proposal outlines the initial $130,000 software package discussed for Corland Partners: a unified backend with isolated company workspaces, starting with Lanson Metals, Leland's Metal, and the first shed-company rollout.

The strategic direction

The strategic direction is a single Corland-owned, endogenous operating system that can grow and scale seamlessly across CRM, contract flow, order tracking, manufacturing, operational execution, and reporting while preserving each company's local workflow.

Shared core

A single Corland backend and data foundation keeps reporting, automation, AI support, and portfolio oversight practical.

Isolated workspaces

Each company can operate in its own branded workspace with its own workflows, settings, ergonomics, and operating habits.

Expandable portfolio

Future companies can be added as additional tenant workspaces rather than rebuilt from scratch each time.

Rollout sequence

The exact dates should be finalized after kickoff access and integration discovery, but the working sequence is clear: Lanson first, Leland's Metal second, then the shed-company rollout.

Lanson Metals first

Highest urgency because Corland Partners has already communicated a quarter-target expectation to Dallas. The practical goal is an initial soft launch first, then continued hardening toward the fuller vision.

  • Confirm Paradigm API access and data handoff details.
  • Launch client catalog management and order workflow.
  • Prepare onboarding path for future Lanson clients.

Leland's Metal second

Leland's Metal is the clearest second launch because Corland Partners can validate the operating-company workflow quickly.

  • Build CRM for lead intake, follow-up, pipeline, and deal management.
  • Keep IdeaRoom as the configuration and pricing source of truth.
  • Add contracts, order visibility, lot/dealer inventory, build/installation, service, and warranty.

Shed company third

The shed rollout follows after the metal architecture, extending the same full operating pattern into the shed-company workflow.

  • Build CRM for lead intake, follow-up, pipeline, and deal management.
  • Contract execution, finished-goods, point-of-sale, manufacturing, delivery, service, and repossession operations.
  • Local workflow flexibility for the specific company.

Scope covered by the initial package

The initial package covers three core software launches. The work is shaped around Corland's current priorities and the long-term need for a reusable operating platform.

Lanson Metals catalog and order solution

A client-facing catalog/order layer that allows shed-company clients to define and maintain metal package catalogs, place orders, and track order status through Lanson Metals.

  • Paradigm API integration path.
  • Catalog/package setup and maintenance.
  • Purchase order creation or review workflow.
  • Status visibility and client communication.

Leland's Metal operational software

A full operating layer for Leland's Metal that combines lead-to-deal CRM with contract execution, order fulfillment, customer service, warranty, and lot/dealer visibility around the existing configuration and manufacturing tools.

  • CRM for lead intake, follow-up, pipeline, and deal management.
  • IdeaRoom as pricing/configuration source of truth.
  • Contract housing, execution, and e-signature workflow.
  • Order fulfillment visibility, lot inventory, sales location access, dealer scope, and build/installation management.
  • Customer service and warranty workflow after fulfillment.

First shed-company rollout

A full operating system for the first shed company, using the shared Corland foundation while combining lead-to-deal CRM with contract execution, finished-goods sales, manufacturing, delivery, customer service, and repossession workflows.

  • CRM for lead intake, follow-up, pipeline, and deal management.
  • Contract execution, finished goods, and point-of-sale workflow.
  • Manufacturing pipeline and delivery scheduling.
  • Mobile document handling and customer signatures.
  • Customer service, repair, and repossession workflows.

Platform architecture

The recommended architecture is a unified Corland backend with isolated company workspaces. It should feel familiar to the HighLevel subaccount model, but with stronger portfolio reporting across accounts.

Unified backend, isolated company surfaces

Corland platform core Identity, tenant registry, reporting, shared modules, audit, configuration.
Lanson Catalogs, orders, Paradigm integration, client onboarding.
Leland's Metal Lead-to-deal CRM, contracts, manufacturing handoff, fulfillment, build/installation, service, warranty.
Shed company Lead-to-deal CRM, POS, manufacturing, delivery, service, repossession workflow.
Future companies Additional tenant workspaces with copied or customized settings.
Portfolio reporting Pipeline, response time, phone activity, lead source, operational status, and company-level comparisons.

Company switching

Corland users should be able to switch between company workspaces without logging out and back in.

Local freedom

Each workspace can have different workflows, triggers, phone settings, permissions, fields, and local processes.

Unified core

Corland gets one organic, endogenous backend for shared control and reporting while each tenant front end can stay highly customized to how that company sells, builds, delivers, and services.

Vendor discipline

Standardizing vendors like e-signature providers and payment merchants reduces backend complexity and makes the platform easier to support.

Included capabilities

The initial package centers on the core capabilities Corland needs to launch the first three operating surfaces: CRM, communications, contract execution, manufacturing, delivery/dispatch, service, reporting, and support.

Included in the initial scope

  • CRM for lead intake, follow-up, pipeline, and deal management.
  • Basic/manual contact sequences tied to CRM records.
  • Twilio-based phone workflow, including internal transfer and true pre-answer round-robin routing.
  • Contract execution, document handling, and standardized e-signature flow.
  • Manufacturing, delivery/dispatch management, and customer service workflows.
  • Lead source, spend, and performance reporting dashboards where access is available.
  • Portfolio-level reporting across tenant accounts.
  • Retainer support to keep the in-scope system dialed in to changing business requirements, ergonomic preferences, and issue support.

Commercial terms discussed

These terms reflect the current working conversation and should be confirmed before final agreement language is prepared.

Initial build package Lanson, Leland's Metal, and first shed-company rollout.
$130,000
Base retainer across the initial three launches Ongoing tuning, issue support, and close operating partnership as requirements and ergonomic preferences evolve.
$6,500/mo
Enhanced first two months Additional cushion for intensive dialing-in and close collaboration after launch.
+$3,000/mo
Additional similar company or branch One-time setup for a similar vertical and environment.
$25,000
Retainer increase per added company or branch For each additional branch/company added to the platform.
+$1,500/mo
Lanson client onboarding Expected to stay under this amount per client, even in larger SKU scenarios.
< $3,000

Working assumptions

These assumptions keep the price and timeline realistic while leaving room for discovery with Corland Partners and the operating teams.

Integration access will be available

We will need timely access to the required business systems, integration endpoints, vendor settings, and reporting sources.

Operating context will be available

Corland will provide construction and implementation context to shorten discovery and reduce rework around system handoffs, production logic, field operations, and local workflow rules.

Standard vendors are acceptable

Corland is comfortable standardizing key vendors such as e-signature providers and payment merchants, similar to how durable software platforms standardize internal processors and service providers.

Some post-launch dialing-in is normal

The first two enhanced-retainer months are intended to give both teams a red-carpet period for sharpening workflows after the initial core launch.

Proposed next step

Corland Partners confirms alignment on this high-level scope and rollout sequence. From there, full discovery calls confirm the detailed requirements, then a final proposal is prepared for deposit and signatures.

Back to top