Proposal prepared for Rocky Mountain Elevator Products Kingdom Way Capital

Multiple build paths. One system that ships.

A focused engagement to consolidate the code you already have, productionize the cab builder, turn the dealer portal into a working system, and keep the project moving with visible weekly progress. I went through the repository before writing a word of this.

Read what I found ↓
RMEP full-glass elevator cab, exterior rooftop installation RMEP full-glass cab · the configurator's flagship use case
Engagement Proposal · 2026
The product

You already make the wow. The software should match it.

These are real RMEP installs. The next step is making the cab builder and dealer portal feel as clear, usable, and dependable as the product itself.

RMEP residential glass cab in a luxury home
Residential glass cab · steel frame, hardwood surround
RMEP full-height glass cab in an open atrium
Full-height glass cab · open atrium install
01 / Repository Audit

I read the codebase first. Here is the honest picture.

You gave me access to the RMEP repository, so I treated this like an engineering review, not a generic proposal. There is real, salvageable work here. There is also fragmentation slowing the project down. The next step is to choose one architecture and carry the strongest pieces forward.

◆ Worth saving

The cab builder is real 3D

It runs on actual WebGL with Three.js and orbit controls. This is not a static mockup. The hard part of a Savaria-class configurator already exists. We refine and productionize it rather than starting over.

◆ Worth saving

A real integration spine

The WordPress plugin already has a provider pattern, REST layer, webhook handling, project tables, Stripe, QuickBooks, and the beginning of a JobBOSS provider.

In plain English, that means the system already has the start of a backbone that can turn a confirmed order into a real production, invoicing, and payment flow.

Needs confirmation

JobBOSS needs proof

The current JobBOSS layer assumes a REST endpoint. JobBOSS does not expose that by default, so the real path needs to be confirmed against your actual setup.

In plain English, we need to confirm that JobBOSS can actually receive an order automatically, then build the integration from that confirmed path inside the partnership.

What's there 5

Parallel build paths in one repo: static site, React SPA, Odoo direction, standalone backend, and WordPress. Some shipped, some reverted, and the work now needs one chosen path.

Activity 166

Commits across roughly six weeks. Real momentum, but spread across approaches that compete with each other.

Carried weight 11

Build archives committed into the repository. A sign of fast iteration without one settled production structure.

Auth status 0

Production logins so far. The portal screens are built and the flow is in place. The login is still a prototype, so real authentication is the main piece to add.

The issue is not the amount of work already done. It is that the work is spread across too many directions at once. The next move is to choose one architecture, carry the strongest pieces forward, add real authentication, and confirm the JobBOSS path early so it can be built properly inside the roadmap.

Tomas Morais · after reviewing PDHutch303/RMEP
Already complete

This audit is done. It would normally be the billed first phase of an engagement. I have folded it into the first month, so we can skip discovery and start building from day one.

02 / Approach

Consolidate. Salvage. Ship. Then iterate.

You described wanting a fast-deployment-and-iterate partner: someone who can get a strong first version live and improve it over time instead of polishing forever before launch. That is exactly the right approach for where this project is now.

STEP 01

Consolidate

Choose one architecture and commit to it. Retire the parallel build paths so every hour after this compounds instead of competing.

STEP 02

Salvage

Keep what is genuinely strong: the WebGL cab builder and the provider-based integration spine. Build forward from those pieces rather than rebuilding from scratch.

STEP 03

Ship

Get a clean, usable first version live on one deploy path. Something customers, dealers, and your internal team can actually use.

STEP 04

Iterate

Refine in weekly stages against an agreed roadmap, with steady, visible progress.

03 / Scope of Work

The four things we build.

Focused on the two development areas you named, the cab builder and dealer portal, plus the foundation work that makes both reliable and the integration path that connects the system back to operations.

AFOUNDATION

One consolidated platform

  • One chosen architecture
  • Parallel build paths retired
  • One clean deploy pipeline, documented
  • A codebase your team can actually maintain
BCUSTOMER FACING

Cab Builder to production

  • Refine the existing 3D configurator into a polished customer-facing experience
  • Add RMEP-specific options Savaria does not offer, including full-glass cab paths
  • Create a cleaner step-by-step configuration flow
  • Add save, export, and quote handoff into your sales process
CDEALER FACING

Dealer Portal, properly built

  • Real authentication and dealer accounts replacing the placeholder login
  • Dashboard, orders, catalog, and project tools wired to live data
  • Order placement connected through to the production workflow
  • Refinement and polish across the existing portal pages
DINTEGRATION

JobBOSS connection

  • Confirm the real supported integration path for your JobBOSS setup
  • Build the order-to-production pipeline on the existing provider spine
  • Test end-to-end against your actual workflow
Included in the partnership: we confirm the JobBOSS path first, then build from the supported connection as part of the ongoing roadmap.
04 / Engagement

A three-month founding partnership.

This is structured as a rolling partnership because the fastest way forward is to get a strong version live, then build on it together. The audit is already complete, so month one starts with consolidation, feasibility, and a usable first version, not another long discovery phase.

MONTH 01
Consolidate and ship live
  • Confirm access, deployment path, and architecture direction
  • Consolidate the current build paths into one chosen platform
  • Get one clean deploy path in place
  • Launch a strong first version that can actually be used
  • Confirm the JobBOSS connection path early and plan the build from there
MONTHS 02–03
Build on the live foundation
  • Refine the cab builder toward production quality
  • Add RMEP-specific options, including full-glass cab paths
  • Build real dealer authentication and account access
  • Wire portal pages to live data and workflow
  • Build the JobBOSS integration from the confirmed path
  • Continue polish across customer, dealer, and internal flows
MONTH 03 · REVIEW
Decide the next roadmap
  • Review what has shipped
  • Prioritize the next stage of cab builder, portal, and integration work
  • Reassess the engagement at the end of the founding rate period
  • Decide how Morascale continues supporting RMEP and Kingdom Way
Weekly check-ins and visible progress An agreed monthly roadmap, not open-ended hours Direct line to Tomas, the person doing the work
05 / Investment

One simple rate. Built for the long game.

Founding partner rate
$2,750 / month
Three-month commitment. Everything in the scope above delivered against an agreed monthly roadmap.
TOTAL ENGAGEMENT $8,250

Deliberately an intro rate

This sits below my standard engagement rate on purpose. I am playing for the long-term relationship, not just this one invoice. RMEP is where I can prove the model. From there, I want to become the build partner Kingdom Way can bring into future portfolio work. We reassess at month three.

Why a retainer, not a fixed quote

The codebase needs consolidation and the JobBOSS path needs confirmation against your actual setup. A retainer means you buy steady, visible progress against an agreed roadmap rather than paying for a fixed estimate built on unknowns.

The audit is already done

I completed the repository audit and architecture review before sending this. It would normally be the billed first phase. It is included, so we start building on day one instead of spending week one discovering what I already found.

+ Architecture consolidation
+ Cab builder productionized
+ Real dealer authentication
+ JobBOSS feasibility and build path
+ One clean deploy pipeline
+ Weekly check-ins and roadmap
06 / Why Morascale

A partner already inside the code.

01

I did the work before the pitch

You are reading findings from your actual repository, not a generic proposal. That is how I run every engagement.

02

Built for fast, real shipping

Get a strong version live, then improve it in clear weekly stages. That matches the fast-deploy-and-iterate cadence you asked for.

03

One point of contact

You work directly with me. No account managers, no handoffs, no telephone game between you and the build.

04

Built for the Kingdom Way model

RMEP is the starting point. If I prove useful here, the bigger opportunity is to become the technical partner Kingdom Way can trust across future builds, integrations, and portfolio-company systems.

07 / Next step

Let's turn the current work into one finished system.

If this direction is right, the next step is a short call to confirm access, architecture direction, and the first-month roadmap. I can start with feasibility, consolidation, and the live-first work immediately.

My goal is to prove the partnership on RMEP, then become the person you bring into the next build when another Kingdom Way company needs software shipped properly.

Approve and start the work Review the agreement (PDF)
Tomas Morais
CEO · Morascale
Tomas@morascale.com · +44 7505 036 741