Operating systemsApex Client OS

Apex Client OS

Projected

Four of the five parts already exist as rails, so this is assembly work on proven pieces rather than a build from nothing.

See it

View it here, in the page
Apex Client OS, prototypeFull screen

Functional scope

Contacts and a pipeline your team actually moves cards through, with the stages named for your trade rather than for software.

A booking calendar that respects your real availability, travel time, and the jobs already on the board.

Invoices with a payment link, and a ledger that recomputes on the server so the total is always the true total.

Agreements sent and signed through Apex Sign, and follow up by email and text through Apex Relay, both already built.

Users and roles

Service operators: cleaning, junk removal, trades, and the veteran owned businesses in that class.

Workflow in practice

Leads arrive and land in the pipeline. Jobs get booked. Agreements go out and come back signed. Invoices send themselves and the follow up runs on its own.

In production

  • One record carries a client from first contact to money received
  • Booking, agreement and invoice all read the same customer row
  • Follow up runs without anyone remembering to send it

Build status

Designed and specified, scheduled to be built.

Three ways to have it

Commission, one time$48,000

Own it, one time. You receive the source, the schema, the deployment, and the documentation. It is yours.

Care, monthly$1,050

Hosting, security updates, storage, authentication, monitoring, and the hours that keep it current. Standard base, before seats.

Licensed Instance, monthly$3,050

Monthly rent, 12 month minimum. We host and run your instance under your name. Half of the first year of rent is credited toward the commission if you convert to ownership.

What Care covers
  • Hosting for the application and its database, with the compute and storage the tier needs
  • Security updates applied on a staging copy first, then to your instance
  • Storage and file delivery, including video where the system uses it
  • Sign in and authentication, kept current with the identity rail
  • Error capture and monitoring, read every week
  • Transactional mail, sent under your own domain
  • A repository security scan and a domain
  • A monthly allowance of senior engineering hours for the care routine: dependency updates, advisor sweeps, log review, and the weekly report
Licensed Instance terms
  • 12 month minimum
  • Teal Apex hosts and runs the instance under your name
  • Your data exports on request at any time
  • 50 percent of the first year of rent credited toward the commission on conversion to ownership

Figures are in US dollars; a rail shared by more than one chosen system is credited once per repeat up to 35 percent of the gross; Care Standard covers hosting, monitoring, updates and security scanning at the vendor prices of August 2026 plus a monthly senior engineering allowance; payment processing fees and app store fees are paid from your own accounts; the Licensed Instance is a 12 month minimum with your data exportable at any time.

Rails used

Stack

  • Next.js
  • Postgres with row level security
  • Stripe
  • Apex Sign
  • Apex Relay

Handover includes

  • Source for the pipeline, booking, invoicing and follow up surfaces
  • Your schema with row level policies
  • Stripe wiring and the ledger model
  • Sign and Relay integration

Add to my ecosystem

Commission Apex Client OS

Tell us how your business runs today and we will send back the arithmetic for this system shaped to your situation.