Orium Studios · the studio behind WallFlow

WallFlow started as one system. Two more were forked from it.

WallFlow is the wallpaper product of Orium Studios. When a business is not wallpaper, the studio forks the same core into a system of its own. The screenshots below are one of those forks, a car brokerage's real system, not a template with a logo dropped on top.

their CRM / deals
The auto brokerage CRM: a deal pipeline in the client's own red on a near-black shell
Their pipeline. Forked from WallFlow's core, not a template.
aagleasing.com
American Auto Group's public website at aagleasing.com
Their public site, same system.
their CRM / promotions
The promotions screen inside the CRM, where offers are authored
Offers are written here.
aagleasing.com/specials
The specials page on the public site, rendered from the CRM's promotions
And appear here, minutes later.
their CRM / deals
The auto brokerage CRM: a deal pipeline in the client's own red on a near-black shell
Their pipeline. Forked from WallFlow's core, not a template.
aagleasing.com
American Auto Group's public website at aagleasing.com
Their public site, same system.
their CRM / promotions
The promotions screen inside the CRM, where offers are authored
Offers are written here.
aagleasing.com/specials
The specials page on the public site, rendered from the CRM's promotions
And appear here, minutes later.

One core, three separate systems

WallFlow is the first. The other two were forked from it by Orium Studios: separate deployments, separate databases, and the trade's own objects and rules in each. Pipeline stages, document types, fields, vocabulary and the visual theme all change; the proven core underneath does not. The red one is a real client.

DraftSentApprovedScheduledPaid
P

Premier Wallcovering

Premium Wallcovering Services

ESTIMATE

#PW-2847

Client:Martinez Residence
Wallpaper · 9 rolls$990.00
Installation labor · 540 ft²$2,700.00
Wall prep & sizing$210.00
Total$3,900.00

Same core, same code, re-skinned and re-configured per business. The red one is a real client.

Forked from WallFlow

What was built on this core

Business names only, no client revenue, no client's customers. Each card is a paraphrase of the studio's own project sheet, which names the file in the repository that proves every claim.

Turnkey sauna building

Your Saunas

A custom CRM for a sauna builder. The room is designed, priced, framed and installed by the same system, because the price depends on a shape that only exists as a drawing while the client is deciding.

  • ▪A 2D planner that prices the room as it is reshaped
  • ▪Wall elevations at one scale, and a set the crew can build from
  • ▪Inbound telephony that raises the caller's record before the phone rings
  • ▪Deposits by card and bank transfer into the contractor's own Stripe account
Read the project sheet on Orium Studios →

Car brokerage

Autobroker

A multi-tenant CRM for car brokers. The rule for what a deal made is written once in the application and once in SQL, in the same change, so the dashboard and the reports can never disagree.

  • ▪One money model, written twice on purpose
  • ▪A co-applicant answers the same credit questions, not fewer
  • ▪Social Security numbers stored as ciphertext, every look at them written down
  • ▪The client's public website in the same deployment, feeding the pipeline
Read the project sheet on Orium Studios →

WallFlow's own sheet, written from the studio's side: oriumstudios.com/work/wallflow

When WallFlow is the wrong choice

Said early, because a wallpaper product sold to a sauna builder costs both sides more than a straight answer. If any of these is true, the studio is the right door.

Your trade is not wallpaper

WallFlow's Material Engine, its labels and its pipeline are shaped around measuring rooms and cutting drops to a pattern repeat. Painting, tile, flooring, saunas, moving, cleaning and car brokerage all have different objects, and configuring a wallpaper product around them is the wrong tool. The studio forks the core into a system with your trade's objects instead.

Your work does not move measure, quote, sign, schedule, install, invoice

That is the pipeline WallFlow enforces, because it is how a wallpaper job runs. If your work is deals, applications, drawings or recurring visits, the stages are different and the product will fight you on every screen.

You want to own the code and the database

WallFlow is a subscription: the data is yours and exportable, the software is not. A system built by Orium Studios is your own repository, your own database and your own Stripe account. If the working relationship ends, nothing switches off.

When WallFlow is the right choice

  • ✓You install wallpaper for a living, solo or with a crew of roughly two to eight.
  • ✓You need roll, panel and yard counts that respect pattern repeat, waste and openings, not an area estimate.
  • ✓You want the estimate, the signature, the schedule, the installer's view and the payment in one place.
  • ✓You want a free wallpaper calculator on your own website that sends you leads with the room already measured.

Systems by trade

The same core, a different system per trade

Only the first of these is WallFlow. The rest describe what the studio built, or would build, for that trade, and each says plainly whether a client runs it today.

Questions people actually ask

Is WallFlow a platform I can configure for my own trade?

No, and that is deliberate. WallFlow is the wallpaper product of Orium Studios. Its calculation, its labels and its pipeline are wallpaper-shaped, and keeping them that way is what makes it good for wallpaper contractors. A business in another trade gets a system of its own from the studio, forked from the same core with that trade's objects.

What does it mean that a system was forked from WallFlow?

The studio copies the parts of WallFlow that are already proven in production, such as authentication, roles, documents, e-signature, payments and notifications, into a separate repository with its own database, then replaces the domain objects: rooms and rolls become sauna plans or vehicle deals. Each fork is its own deployment and shares no data with WallFlow or with any other client.

Who builds the custom systems, and where?

Orium Studios LLC, an automation studio in Sacramento, CA, run by Eugene Romanov. The same studio built and operates WallFlow. Its work, its process and its prices are published on https://oriumstudios.com, and this page does not restate the prices, because one number cannot live in two places.

What does a system of my own cost?

The studio publishes that itself, with sources and the date each was read, at https://oriumstudios.com/custom-crm-cost. WallFlow's own pricing, the Pro and Team plans and the Launch call, is on this site's pricing page. Nothing on this page is a price for the studio's work.

How long does a fork take?

In the studio's own words, weeks rather than months, because the core is already running and only the trade-specific part is new. The exact timeline is scoped in writing before work starts.

Who owns the code and the data in a system the studio builds?

The client does. The repository, the database and the Stripe account are registered in the client's name. Work that touches personal data is done under a written Data Processing Agreement with the client as the controller. The studio states this itself on its custom CRM page.

Where do I start if WallFlow is not for me?

With the studio's free audit at https://oriumstudios.com/free-audit: a short recorded walkthrough of where your lead flow leaks and what to build first, delivered the same day, with no call unless you want one.

Not wallpaper? Start with the audit.

Orium Studios records a short walkthrough of where your lead flow leaks and what it would take to close it. Free, delivered the same day, and there is no call afterwards unless you want one.

Or write a sentence here. It reaches the studio's founder directly, or on WhatsApp.

Tell me what your business does and what is breaking. No pitch deck, no discovery invoice.

Either an email or a phone number is enough. Nothing is shared with anyone.