What we build

Two products, one question.

Both of these are about giving real work to something that runs without you, and being able to check afterwards what it did. One does it for a back office. The other does it for an entire company.

Corebizy

Early access

An AI back office for service businesses. Corebizy answers the inquiry, books the work, sends the invoice, takes the payment and follows up, so the owner can stay on the job instead of behind a desk.

What a client gets is a CREW — a Customer Relations and Engagement Workspace. Six roles, each owning a surface their customers actually touch. The client sets the greeting, the wording and the tone, so CREW sounds like their business rather than like ours.

Built for plumbers, electricians, HVAC techs, landscapers, cleaners, handymen, painters and general contractors — businesses of one to a few people, where the owner is also the dispatcher.

corebizy.ai

CREW roles

Receptionist: Answers the first contact, qualifies it, routes it.
Office Manager: Coordinates the rest, and escalates what needs a person.
Scheduling: Books and rebooks, so only confirmed work shows up.
Invoicing and payments: Sends what is owed and collects it.
Follow-up: Quotes to chase, check-ins to make, reviews to ask for.
Support: Handles the questions that arrive after the job is done.

Corebizy is pre-revenue and onboarding its first clients, in the United States only. There is no waitlist theatre here: if it is not built, we do not say it is.

Riff

Open source · Apache-2.0

Give it a company name, a line of business, and two names — yours and your CEO’s. It founds the company, and the CEO hires the rest.

There is no roster in the repository. Nothing in it knows what departments your company should have, what its staff should be called, or what it should build. One agent starts work, and everything after that is a decision somebody in the company made and can be read back.

Roles and departments are free text the staff invent. Only the four tiers are fixed, because the tier is the one thing the policy gate switches on — which lets the org chart become anything without the enforcement code learning a new shape.

The staff get a real shell, a compiler and a package manager, because agents cannot build anything worth reviewing without them. That is handed over inside a container rather than on your machine, and the credential is read from your password manager at launch — never written to a file, never passed as an argument.

github.com/lafollett-labs/riff

The six rules

Work well together.
Work however you see fit inside your mandate.
Work may go to the outside world, but it always lands as a draft.
Only the treasurer may spend, and only up to a daily cap.
If the board is not around, do not stop.
The commons holds forty documents. To add one past that, remove one.

Four of the six are enforced in code. Every action an agent attempts crosses one gate before it happens, and no tool goes around it. The other two are a disposition and a property of the scheduler, and are deliberately left unenforced.

Four tiers, and nothing else fixed

Riff's four authority tiers, who occupies each, and what the policy gate enforces for them.
Tier	Who	What the gate does
board	Humans.	Terminal authority. Bypasses the gate because it is the gate.
executive	The CEO.	Signs hires and cross-desk writes.
lead	Whoever the CEO hires.	May hire, with the CEO’s signature.
member	Whoever the leads hire.	Works inside a mandate.

Corebizy is a product of LaFollett Labs LLC. Riff is released under the Apache License 2.0 and is free to use, fork and run. Questions about either reach a person.