Skip to content
Sites by Nu
All work
Client projectProperty servicesOperion implementation · first client

Supercharged Enterprise

Operion’s first client: a property-preservation company running evictions, trash outs, junk removal and lawn care through the platform, configured with its own brand and pricing.

superchargedenterprise.com
Supercharged Enterprise — the live interface
My role
Architect and developer.
Built for
Property services
Project type
Operion implementation · first client
Built with
Next.js · TypeScript · Redis (Upstash) · Vercel Blob · Vercel

The story

What problem existed, and what we built.

The problem

Proving the J Kiss operations platform could carry a second business with different services, different pricing and a different brand.

What I built

An adapted copy of Operion on its own codebase and deployment, with its own identity and service catalog. Booking, dispatch, payroll and reliability work is ported between the two codebases.

What it had to achieve

  • Run a second business on Operion's code
  • Prove the booking path end to end in production

The customer's experience

A property manager requests a clear-out, gets a price, and books it.

What customers can do

  • Quote wizard
  • Online booking
  • Job tracking
  • Careers applications

The owner & staff experience

Operion configured for the client’s services, team and pricing.

What the business can do

  • Dispatch and crew scheduling
  • Operations dashboard
  • Payroll
  • Alerting

How it works

Architecture & integrations.

How the application, data, access controls, and connected services work together.

Reliability that was proven, not assumed

Booking writes are serialized so two simultaneous requests cannot claim the same slot, and alert delivery was tested rather than trusted — an alerting system nobody has ever seen fire is not an alerting system.

Design decisions

The choices that shaped it — and why.

Diagnose with evidence, not theory

Two plausible explanations for low bookings were both disproven by driving the real booking path in production. The remaining issue is reaching customers, not the software — which is a different problem with a different fix.

How it was built

Development process

  1. 1Adapted Operion for its first client, Supercharged Enterprise
  2. 2Ran a reliability wave — booking idempotency, capacity admission, payroll locks
  3. 3Verified the booking flow end-to-end in production
  4. 4Proved alert delivery

Technical overview

Technology & implementation

Technology stack

  • Next.js
  • TypeScript
  • Redis (Upstash)
  • Vercel Blob
  • Vercel

Implementation scope

Architect and developer.

Related projects

You might also want to see

Operion — interface
LiveGrowing service companies

Operion

Multi-tenant operations platform · Project

www.jkissllc.com/operion

The operations platform built inside J Kiss LLC, with multi-company support designed in. J Kiss runs on the primary deployment; Supercharged Enterprise runs an adapted copy from its own codebase.

Read the case study
J Kiss LLC — interface
LiveLocal service businesses

J Kiss LLC

Operations platform for a service business · Project

jkissllc.com

A Dallas–Fort Worth hauling company that takes quotes, books jobs, dispatches crews, hires staff and runs payroll from one connected system rather than six disconnected ones.

Read the case study

Want something like this for your business?

Tell me how your days go and what you'd like to stop doing by hand. I'll tell you honestly what would help.