Routing Engine · v3 specification

One qualification engine.
Every destination.

Opportunities enter through four input channels and are evaluated in parallel on company profile, client need, and regulatory classification. Qualified opportunities route to the appropriate internal lane; non-fits are referred to third-party partners for a fee. Every outcome feeds the monetization and analytics layer.

Routing engine · Live schematic

Every opportunity enters one door.
Qualified, then routed.

01Input channels
Outbound origination
Targeted prospecting
~2,400 / qtr
Referral sources
Partner network
~860 / qtr
Source inputs
Inbound intake
~1,100 / qtr
Data providers
Signal feeds
continuous
02Qualification engine
Evaluating
-
awaiting input
01
Company profile
Sector · stage · revenue · geography
-
02
Client need
Capital · production capacity · advisory
-
03
Regulatory class
Solicitation · licensing · entity match
-
Parallel screen · company profile, client need, regulatory classification
03Routing destinations
Fund allocation
Investment thesis fit
Government contracting
Procurement pipeline
Securities entity
Licensed broker-dealer
Real estate group
Asset-class match
General consulting
Advisory engagement
Partner referral
Third-party handoff · fee
Stepwise

Four steps, always.

01

Intake

Outbound origination, referrals, inbound submissions, and data-provider signals are consolidated into a single normalized record.

02

Qualify

Parallel evaluation of company profile, client need, and regulatory classification. Criteria are versioned; every evaluation is recorded.

03

Route

Internal lane match (fund, government, securities, real estate, consulting) or third-party referral with fee capture.

04

Feedback

Outcomes feed the analytics loop. Targeting and routing thresholds refine over time; partner performance is tracked.

The qualification criteria
Dimension 01

Company profile

Objective filters that describe the counterparty and bound the set of lanes it could conceivably match.

  • SectorIndustry classification and sub-sector context
  • StagePre-revenue through late-growth; public-private status
  • RevenueTrailing twelve months, growth trajectory, unit economics
  • GeographyJurisdiction of incorporation, operational footprint
Dimension 02

Client need

What the counterparty is actually asking for, expressed as a scope that maps to a specific service tier or lane.

  • CapitalRaise size, round type, timeline, use of proceeds
  • CapacityProduction support for advisors, banks, broker-dealers
  • AdvisoryGeneral consulting, operational, or growth support
  • ContractingGovernment procurement opportunities and pipelines
Dimension 03

Regulatory classification

The decisive screen. Whenever a request touches licensed activity, the engine halts internal routing and initiates the handoff protocol.

  • SolicitationAny direct investor solicitation triggers securities handoff
  • NegotiationTerm discussions or negotiation are out of scope for Apex
  • LicensingLicensed activities route to the appropriately licensed partner
  • DisclosureAll handoffs are logged; counterparty is notified in writing
Feedback loop
Monetization

Referral fee capture

Every third-party handoff produces a recorded referral relationship and a compensation event, independent of deal outcome.

Network

Partner development

Partner performance is tracked by disposition and conversion. Strong partners get more flow; weak ones are rotated out.

Model

Routing optimization

Criteria thresholds refine against realized outcomes. The qualification surface is versioned and auditable.

Put an opportunity through the engine.