What you need, built,
live after your yes.
Agents build; you approve every release.
New pages and sections, a customer portal, an internal tool, an integration or an automation, drafted and built by agents from your records; nothing goes live before your yes.
Product · Build · your team
Your team: five seats, one job.
The same five seats run every module, so every report reads the same way. You approve what goes out.
01 · Lead
Product lead
Turns your request into a scoped build with a date, and chases what is late
02 · Analyst
Requirements analyst
Writes the spec from your records and tools, and checks what already exists
03 · Makers
Page, portal, tool and automation builders
Draft and build the pages, screens, connections and automations
04 · Reviewer
QA & access check
Tests each build on sample data and checks who can see what before you do
05 · Operator
Release desk
Puts live only what you approved, one change at a time, and can roll it back
Across every module
- Chief of staff (Hue) Reads every Lead’s plan, settles conflicts between modules and writes the one-page 7 AM brief
- Head of analytics One attribution truth, to the paid invoice, that every Analyst reads
- Compliance officer Consent, anti-spam rules, claims and voice policy; can veto any Reviewer’s pass
What you get each month
Loops that close, counted every month.
One module includes its team and 500 tasks a month, pooled across everything you buy. A task is one finished item; heavier items count for more.
Request to release
- Counted
- builds shipped
- Judged on
- shipped on the date you approved; used after launch
Automations
- Counted
- automations running
- Judged on
- manual steps replaced (an estimate)
Beyond the pool, packs of extra tasks under a monthly cap you set. We never promise a result: these are the measures we report against.
Product · Build · what’s inside
Eight features, one module.
6 live, 1 in early access, 1 coming. Open a card for what it does and what it connects to.
LiveScreens and internal tools
Ask for a screen or a tool; Hue draws it from your own records and saves it as a page of your app, a checked spec, never code.
Runs inside Humonix, nothing to connect.
LiveSite pages and sections
New pages and sections drafted in your brand, reviewed, then published by an owner; your domain goes live only once it is verified.
Runs inside Humonix, nothing to connect.
LiveCustomer portal
A space your customers sign in to with an email code: their quotes, documents to sign, jobs, invoices and requests. You pick what shows.
Runs inside Humonix, nothing to connect.
LiveAutomations
When this happens, do that: each one reads as a sentence and runs on a sample event first; sending, money and stock always wait for a person.
Runs inside Humonix, nothing to connect.
LiveYour API and webhooks
API keys with scopes and signed webhooks, so what we build connects to your other systems; owners only.
Runs inside Humonix, nothing to connect.
LiveBuild requests
Ask for what you need built; each request is filed with its scope and status, and you approve the build before it starts.
Runs inside Humonix, nothing to connect.
ComingConnectors for your other tools
A connector for a system we do not connect yet, drafted by agents and reviewed by an engineer before it reads or writes anything.
Runs inside Humonix, nothing to connect.
Early accessB2B buyer portal on your store
Buyers sign in on your store to see their company’s prices, order with a PO, approve, reorder and save carts.
Connects to Your website
Live: works today. Early access: built, switched on for you after a setup step or a provider’s review. Coming: planned, never sold as working. Anything that goes out waits for your approval.
Good to know
- Screens and tools are checked specs drawn from your own records, never code we run on your systems; each page is saved only when someone saves it.
- New site pages publish only after an owner’s approval, and your domain serves them only once it is verified and switched live with you.
- Senior engineering time is extra FDE hours, approved in advance; a connector for a system we do not connect yet is coming, not sold as working.
One module (Build) · $350/mo, the Product department (both modules, setup included, a monthly department report) · $600/mo, all twelve with Head of Digital, agents · $3,000/mo, or Head of Digital + Taylor · $6,000/mo.
See pricing