Projects

Impensa Projects

Ten real projects in the impensa sector, from an order to a delivered, billed shipment. Involvement in a project means participating in the project and sharing in its actual net revenue — the Participant Pool is 10% of each project’s net revenue, distributed monthly among qualifying participants. It is not a yield on IMP and no return is promised.

Each project has a participation gate: hold IMP worth 1% of the project’s value (in CAD). The gate is a balance check only — nothing is spent, transferred, or locked, ever. Holds stack: your balance must cover the sum of the gates of every project you join. Involvement stays active only while your wallet is connected and the hold is met; if the balance drops or the wallet disconnects, involvement suspends and resumes automatically when the hold is restored.

Need IMP? Buy IMP on XMarkets · Mine IMP on Omnichain

Wallet not connected. Project details and gate figures are public; connect a wallet to see your own gate state and join.
The gate gradient: $420 → $480 → $1,850 → $2,400 → $8,600 → $9,400 → $46,000 → $185,000 → $1,200,000 → $4,800,000 of IMP (CAD value of the hold, 1% of each project’s value)

Single-Tractor Highway Fleet T1 Bootstrap

One highway tractor and trailer, owned outright and leased to a working owner-operator — the smallest fleet that is still a fleet.

Project value$42,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Tractor and trailer purchased, titled to the project, and recorded in the ERP asset register
Participation gateHold ≈ — IMP ($420 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Monthly lease paid by the operating driver, the maintenance-program fee that keeps the unit serviced on schedule, and trailer hire when the trailer works separately. The project owns the asset; the operator earns from hauling; the lease is priced below general rental because the maintenance record travels with the truck.

What involvement gets you: The pool share; the participant dashboard with the unit's lease state, maintenance currency, and net revenue reporting; milestone notifications; and a maintenance-slot priority for a holder's own truck at the project's servicing arrangement.

Knowledge assets: the unit ownership file — purchase record, title, and the valuation note for the tractor and trailer — kept in the ERP as the project's standing asset record; the maintenance book — service intervals, completed services, and the cost-per-kilometre record for the unit; the lease standard — the owner-operator lease terms and the inspection routine at lease start and return, written as standing procedure.

Recurring involvement actions: the operating driver lodges monthly odometer, hours-of-service, and defect reports through the ERP, and the project receives and records them against the unit file; participants join the monthly unit review — lease state, maintenance currency, cost per kilometre — minuted into the project record; holders confirm the unit's service bookings against the maintenance book each quarter.

Reporting commitment: monthly operating report from the ERP ledger — lease receipts, maintenance performed and due, kilometres run, revenue and costs. Sector-state indicators: unit availability days, maintenance currency, cost per kilometre. The reporting obligation binds the operator named at launch.

Milestones: (1) Tractor and trailer purchased, titled to the project, and recorded in the ERP asset register · (2) Owner-operator lease signed and first month completed on record · (3) First scheduled service cycle completed through the maintenance book · (4) Twelve months of unit records complete — lease, maintenance, and cost per kilometre unbroken

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Harbour Workboat Fleet T1 Bootstrap

One used harbour workboat, owned outright and worked on crew transfers, stores runs, and light towing out of a single harbour.

Project value$48,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Workboat purchased, surveyed, titled to the project, and recorded in the ERP asset register
Participation gateHold ≈ — IMP ($480 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Day-rate and half-day charters paid by harbour users, standing retainers from operators who need guaranteed availability, and per-job towing and stores-run fees. Ownership is the economics: a chartered-out owned hull earns its keep across many small customers no single one of whom could carry a vessel.

What involvement gets you: The pool share; the participant dashboard with charter days, maintenance and certification state, and net revenue reporting; milestone notifications; and charter priority for a holder's own harbour work at the project's standard rates.

Knowledge assets: the vessel file — purchase record, survey, title, and certification documents — kept in the ERP as the standing asset record; the harbour operations book — charter log, tidal and berth notes for the home harbour, and the rate record by job type; the maintenance standard — engine hours, haul-out schedule, and safety-equipment checks written as standing procedure.

Recurring involvement actions: charter customers lodge job requests and confirmations through the ERP before the vessel sails, and the project receives and records them against the charter log; participants join the monthly vessel review — charter days, maintenance state, certification currency — minuted into the project record; holders confirm the haul-out and service bookings against the maintenance standard each season.

Reporting commitment: monthly operating report from the ERP ledger — charter days and jobs, engine hours, maintenance performed and due, revenue and costs. Sector-state indicators: charter days per month, vessel availability, certification currency. The reporting obligation binds the operator named at launch.

Milestones: (1) Workboat purchased, surveyed, titled to the project, and recorded in the ERP asset register · (2) First five paid charters completed on record · (3) First standing retainer signed with a harbour operator · (4) First haul-out and service cycle completed through the maintenance standard

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Regional Courier Van Fleet T2 Startup

Twelve cargo vans owned as one fleet and leased to courier operators across a region, maintenance included on one record.

Project value$185,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Twelve vans purchased, titled to the project, and recorded in the fleet register
Participation gateHold ≈ — IMP ($1,850 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Per-van monthly leases paid by the operating couriers, maintenance-program fees, and replacement-vehicle cover fees when a van is in the shop. The pool earns because utilization stays high: a van coming off one lease is serviced, recorded, and re-leased against standing demand instead of sitting.

What involvement gets you: The pool share; the participant dashboard with fleet utilization, lease states, maintenance currency, and net revenue reporting; milestone notifications; and a lease-slot priority for a holder's own delivery business at the project's standard rates.

Knowledge assets: the fleet register — purchase records, titles, and per-van valuation notes for all twelve units — kept in the ERP as the standing asset record; the van maintenance book — service intervals by unit, completed services, and cost per kilometre by van; the courier lease standard — lease terms, driver and vehicle inspection routines, and the off-lease condition standard, written as standing procedure.

Recurring involvement actions: operating couriers lodge monthly odometer, defect, and route-volume reports through the ERP, and the project receives and records them against each van's file; participants join the monthly fleet review — utilization, leases in force, maintenance currency — minuted into the project record; holders confirm service bookings for their own vehicles against the fleet's servicing arrangement each quarter.

Reporting commitment: monthly operating report from the ERP ledger — vans leased of twelve, utilization, maintenance performed and due, revenue and costs. Sector-state indicators: fleet utilization %, maintenance currency, cost per kilometre by unit. The reporting obligation binds the operator named at launch.

Milestones: (1) Twelve vans purchased, titled to the project, and recorded in the fleet register · (2) First eight vans on lease with records live in the ERP · (3) Full fleet leased with the maintenance book current on every unit · (4) First replacement cycle — highest-kilometre van rotated out and replaced on the record

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Light Aircraft Cargo Fleet T2 Startup

Two used single-engine cargo aircraft, owned and chartered for regional freight into northern and coastal strips.

Project value$240,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Both aircraft purchased, registered to the project, and recorded in the ERP asset register
Participation gateHold ≈ — IMP ($2,400 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Per-trip and per-hour charters paid by shippers and resupply programs, plus standing availability retainers from customers who need guaranteed lift. Owned aircraft on charter earn across many customers; the ERP record — hours, maintenance, charter history — is what keeps insurance, certification, and customer trust in force.

What involvement gets you: The pool share; the participant dashboard with flight hours, charter state, maintenance currency, and net revenue reporting; milestone notifications; and charter priority for a holder's own urgent freight at the project's standard rates.

Knowledge assets: the aircraft files — purchase records, registration, airworthiness and inspection documents for both aircraft — kept in the ERP as the standing asset record; the charter operations book — strip and route notes, load and range tables, and the rate record by route; the maintenance standard — inspection intervals by hours and calendar, completed checks, and the defect-reporting procedure, written as standing procedure.

Recurring involvement actions: charter customers lodge flight requests and load confirmations through the ERP before each trip, and the project receives and records them against the charter log; participants join the monthly fleet review — hours flown, charters completed, maintenance currency — minuted into the project record; holders confirm inspection and service bookings against the maintenance standard each quarter.

Reporting commitment: monthly operating report from the ERP ledger — flight hours by aircraft, charters completed, maintenance performed and due, revenue and costs. Sector-state indicators: hours flown, aircraft availability, inspection currency. The reporting obligation binds the operator named at launch.

Milestones: (1) Both aircraft purchased, registered to the project, and recorded in the ERP asset register · (2) First ten paid charters completed on record · (3) First standing resupply retainer signed · (4) First full inspection cycle completed on both aircraft through the maintenance standard

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Highway Truck Fleet & Maintenance Garage T3 Growth

Twenty-five tractors and thirty trailers owned, plus the project's first owned maintenance garage servicing the fleet and outside fleets.

Project value$860,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Fleet purchased and titled, garage building secured and fitted with lifts and tooling, all recorded in the asset register
Participation gateHold ≈ — IMP ($8,600 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Monthly fleet leases, trailer hire, garage labour and parts margin on outside work, and maintenance-program fees from leased units serviced in-house. Owning the garage cuts the fleet's downtime and turns the fleet's own maintenance spend into project revenue.

What involvement gets you: The pool share; the participant dashboard with fleet utilization, garage throughput, maintenance currency, and net revenue reporting; milestone notifications; and garage booking priority for a holder's own trucks at the project's standard rates.

Knowledge assets: the fleet and garage asset register — titles and valuation notes for every tractor and trailer, the garage building and equipment file — kept in the ERP as the standing asset record; the garage operations book — bay scheduling, job cards, and the cost record by repair type; the fleet maintenance standard — service intervals by unit, inspection routines, and the downtime record by cause, written as standing procedure.

Recurring involvement actions: lessees lodge monthly odometer, hours-of-service, and defect reports through the ERP, and the project receives and schedules them against the garage book; participants join the monthly fleet-and-garage review — utilization, downtime, bays worked — minuted into the project record; outside garage customers confirm their bookings and job cards against the record each month.

Reporting commitment: monthly operating report from the ERP ledger — units leased of twenty-five, fleet downtime days, garage jobs completed by type, revenue and costs. Sector-state indicators: fleet utilization %, downtime days, maintenance currency, garage bay utilization. The reporting obligation binds the operator named at launch.

Milestones: (1) Fleet purchased and titled, garage building secured and fitted with lifts and tooling, all recorded in the asset register · (2) First fifteen tractors on lease with maintenance live in the ERP · (3) Garage selling spare bays to outside fleets at steady weekly volume · (4) Fleet downtime held under the standard for a full quarter, reported from the record

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Coastal Vessel Fleet T3 Growth

Three used coastal vessels owned and chartered on coastal routes — materials, fuel, equipment, and community freight.

Project value$940,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Three vessels purchased, surveyed, titled to the project, and recorded in the asset register
Participation gateHold ≈ — IMP ($9,400 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Voyage charters paid by shippers and construction programs, monthly operating contracts with coastal customers, and backhaul rates on return legs. Owned vessels earn on both directions when the record is used to sell the empty leg instead of sailing it for nothing.

What involvement gets you: The pool share; the participant dashboard with voyage state, fleet availability, maintenance and certification currency, and net revenue reporting; milestone notifications; and charter priority for a holder's own coastal freight at the project's standard rates.

Knowledge assets: the vessel files — purchase records, surveys, titles, and certification for all three vessels — kept in the ERP as the standing asset record; the coastal operations book — route and port notes, tidal and seasonal limits, and the rate record by route and cargo; the fleet maintenance standard — haul-out cycles, engine and hull programs, and safety-equipment standards, written as standing procedure.

Recurring involvement actions: charter customers lodge cargo and schedule confirmations through the ERP before each voyage, and the project receives and records them against the voyage log; participants join the monthly fleet review — voyages completed, availability, maintenance state — minuted into the project record; holders moving coastal freight confirm their consignments against the voyage record at each sailing.

Reporting commitment: monthly operating report from the ERP ledger — voyages by vessel and route, tonnes carried, maintenance performed and due, revenue and costs. Sector-state indicators: voyages per month, fleet availability, backhaul utilization, certification currency. The reporting obligation binds the operator named at launch.

Milestones: (1) Three vessels purchased, surveyed, titled to the project, and recorded in the asset register · (2) First ten paid voyages completed on record · (3) First monthly operating contract signed with a coastal customer · (4) First haul-out cycle completed across the fleet through the maintenance standard

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Regional Air Cargo Fleet T4 Established

Six turboprop cargo aircraft owned, flying scheduled regional freight and charters, with the spares pool and hangar that keep them airworthy.

Project value$4,600,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) Six aircraft purchased and registered, hangar fitted and spares pool stocked, all recorded in the asset register
Participation gateHold ≈ — IMP ($46,000 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Scheduled freight contracts paid by resupply programs and regional shippers, per-trip charters, and third-party maintenance work sold from the fleet's own hangar capacity. The spares pool and hangar are in the project because dispatch reliability — the thing customers actually pay for — is built out of them.

What involvement gets you: The pool share; the participant dashboard with fleet hours, schedule performance, maintenance currency, and net revenue reporting; milestone notifications; and freight capacity priority for a holder's own regional consignments at the project's standard rates.

Knowledge assets: the aircraft files — purchase records, registrations, airworthiness and inspection documents for all six aircraft, plus the spares-pool inventory — kept in the ERP as the standing asset record; the schedule operations book — route economics by lane, load factors, and the on-time record by route; the fleet maintenance standard — inspection programs by hours and cycles, hangar job cards, and the defect and deferral procedure, written as standing procedure.

Recurring involvement actions: freight customers lodge consignments and schedule confirmations through the ERP ahead of each flight, and the project receives and records them against the flight log; participants join the monthly fleet review — hours, schedule performance, maintenance currency — minuted into the project record; holders confirm their standing freight requirements against the schedule each quarter, and the project plans capacity against them.

Reporting commitment: monthly operating report from the ERP ledger — hours by aircraft, tonnes carried by route, schedule performance, maintenance performed and due, revenue and costs. Sector-state indicators: fleet hours, on-time performance, aircraft availability, inspection currency. The reporting obligation binds the operator named at launch.

Milestones: (1) Six aircraft purchased and registered, hangar fitted and spares pool stocked, all recorded in the asset register · (2) First scheduled route operating on a published timetable · (3) Scheduled network at three routes with on-time performance reported from the record · (4) Hangar selling third-party maintenance at steady monthly volume

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

National Truck Fleet, Garage & Supply Depot Network T5 Large

300 tractors, 450 trailers, four owned garages, and six owned supply depots — the land operation owned end to end at national scale.

Project value$18,500,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) First region complete — fleet tranche, one garage, and two depots owned and recorded, operating as one system
Participation gateHold ≈ — IMP ($185,000 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Fleet leases to carriers and contract operators, garage labour and parts margin on the project's own and outside fleets, depot sales of parts, tyres, and fuel to the fleet and to outside operators, and trailer hire. The network earns on every turn of the wheel it owns — and on a share of the wheels it doesn't.

What involvement gets you: The pool share; the participant dashboard with fleet utilization, garage throughput, depot stock and sales, and net revenue reporting; milestone notifications; and network service priority — garage bays and depot supply — for a holder's own fleet at the project's standard rates.

Knowledge assets: the network asset register — titles and valuation notes for every tractor, trailer, garage, and depot — kept in the ERP as the standing asset record; the depot operations book — stock standards by depot, reorder points, and the parts-movement record across the network; the network maintenance standard — service intervals, cross-regional job transfer procedure, and downtime reporting by cause and region, written as standing procedure.

Recurring involvement actions: lessees and garage customers lodge service, defect, and supply requirements through the ERP, and the network receives and schedules them against garage and depot capacity; participants join the monthly network review — utilization, downtime, depot turns — minuted into the project record; holders with fleets confirm their standing parts and service requirements against the depot record each quarter.

Reporting commitment: monthly operating report from the ERP ledger — units leased of 300, downtime days by region, garage jobs by type, depot sales and stock turns, revenue and costs. Sector-state indicators: fleet utilization %, downtime days, depot stock turns, maintenance currency. The reporting obligation binds the operator named at launch.

Milestones: (1) First region complete — fleet tranche, one garage, and two depots owned and recorded, operating as one system · (2) Half the network in service: 150 tractors leased, two garages and four depots operating · (3) Full network in service with cross-regional maintenance transfers running on the record · (4) First full year of network reporting — utilization, downtime, and depot turns published from the ledger

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Ocean & Coastal Vessel Fleet with Port Supply Depots T6 Mega

Eighteen vessels owned — coasters, tugs, barges, one ice-class cargo vessel — with three owned port supply depots behind them.

Project value$120,000,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) First depot complete and first six vessels owned, surveyed, and in service on the record
Participation gateHold ≈ — IMP ($1,200,000 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: Voyage and time charters across the fleet, northern resupply contracts on the ice-class vessel, depot throughput and storage fees from the fleet's own and outside vessels, and vessel services (fuel, stores, equipment hire) sold at the depots. The depots earn from every vessel that works the port, including the ones the project doesn't own.

What involvement gets you: The pool share; the participant dashboard with fleet deployment, depot throughput, maintenance and certification state, and net revenue reporting; milestone notifications; and charter and depot priority for a holder's own marine freight at the project's standard rates.

Knowledge assets: the fleet and depot asset register — surveys, titles, and certification for all eighteen vessels, and the depot property and equipment files — kept in the ERP as the standing asset record; the marine operations book — route, port, and seasonal (including ice) operating notes, and the rate record by trade; the fleet maintenance standard — drydock and haul-out programs by vessel, classification and certification tracking, and the safety standard, written as standing procedure.

Recurring involvement actions: charterers and depot customers lodge cargo, schedule, and service requirements through the ERP ahead of each movement, and the project receives and records them against the voyage and depot logs; participants join the quarterly fleet review — deployment, drydock program, depot performance — minuted into the project record; holders moving marine freight confirm their consignments against the continuous voyage record at each hand-off.

Reporting commitment: monthly operating report from the ERP ledger — voyages and tonnes by vessel and trade, depot throughput and storage, maintenance and drydock state, revenue and costs. Sector-state indicators: fleet deployment days, tonnes carried, depot throughput, certification currency. The reporting obligation binds the operator named at launch.

Milestones: (1) First depot complete and first six vessels owned, surveyed, and in service on the record · (2) Ice-class vessel delivered and first northern resupply season completed · (3) Full fleet of eighteen vessels and three depots operating as one system · (4) First full drydock cycle completed across the fleet through the maintenance standard

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.

Integrated Air–Land–Sea Asset Ownership Program T7 Giga

One program owning the asset base of a national logistics system in stages — aircraft fleets, truck fleet, vessel fleets, garages, and depots on one record.

Project value$480,000,000 CAD
Participant Pool10% of net revenue, monthly
Next milestone(1) First stage — one mode's fleet with its garage and depot support — owned and operating end to end on the program record
Participation gateHold ≈ — IMP ($4,800,000 CAD) — 1% of project value
Your stateWallet not connected

What it does & revenue model: The stages' own earnings as they come online: fleet leases and charters across air, land, and sea; garage services; depot throughput, storage, and supply sales — each stage earning from its own assets and reported inside the one program record. No stage proceeds on the promise of a later one; each is financed, owned, and operated on its own record.

What involvement gets you: The pool share across program stages; the participant dashboard with per-stage asset, deployment, and financial reporting; stage-gate briefings before each stage commitment with the running stages' records in hand; and a permanent place in the program's participant registry as stages come online over the build-out.

Knowledge assets: the program asset register — titles, surveys, registrations, and valuation notes for every asset in every stage — kept in the ERP as the standing record of what the program owns; the stage-gate book — the commitment criteria, operating results, and lessons record for each stage, kept as the program's decision history; the integrated maintenance standard — how fleet, garage, and depot standards from the smaller projects compose into one program-wide standard, written as standing procedure.

Recurring involvement actions: participants lodge freight and service requirements through the ERP as each stage opens, and the system receives and plans them against the stage record; participants join the quarterly stage-gate review — stages live, assets owned, deployment and revenue by mode — minuted into the project record; holders moving freight across modes confirm their consignments against the continuous movement record at each hand-off.

Reporting commitment: quarterly stage-gate report with monthly operating figures for each live stage, from the ERP ledger — assets owned by class, deployment by mode, garage and depot performance, revenue and costs per stage. Sector-state indicators: assets owned by class, deployment days by mode, maintenance currency across fleets, depot throughput. The reporting obligation binds the operator named at launch.

Milestones: (1) First stage — one mode's fleet with its garage and depot support — owned and operating end to end on the program record · (2) Second mode integrated, with cross-mode consignments moving on assets the program owns at every leg · (3) All three modes operating as one owned system with per-stage reporting · (4) Second-region replication of the full system committed on the first region's operating record

Status: Design — awaiting launch. Participation: hold 1% of the project’s value in IMP, held, never spent.