Chapter 01 / Homi

Homi connects all.

Homi is the AI assistant inside House. Ask about the work, review proposed changes, and put repeat drafting on a schedule—with a person deciding what happens next.

Built for ecommerce email agencies.

The conviction behind Homi

AI is an amplifier of Human expression.

Jordan ParisFounder, House · September 22, 2026

Context. A proposal. Your decision.

  1. Tell Homi what happened.

    Ask a question or give it the recap. Homi can find client and work context, published knowledge, permitted calls, team information, and capacity within the access available to you.

  2. Look at what would change.

    For supported edits, Homi proposes a before-and-after view. You can review the actual change before applying it. If the underlying record has changed, the proposal needs another look.

  3. Keep your judgment in the loop.

    A person applies the change. Applied changes have a history, and eligible changes can be undone. Homi does not approve its own proposals.

From Homi · Cedar Goods

A first draft, already on the desk.

Every Monday
Weekly client reportWork in House, selected Klaviyo results, and the agency’s reporting SOP. A draft with a Check before sending section.
After a won-deal handoff
Sales handover bundleBrand context, promises, open questions, and first steps for the delivery team to review.
When client health turns At risk
Recovery planAn internal draft for the people responsible for the relationship.
Each morning
Due, overdue, and urgentA personal breakdown built from the work itself. This list uses no AI.
Illustrative example · fictional agency and people. Illustrative workflow. Reports and event outputs are drafts. A person reviews and sends a report to the brand.

Bring the agency’s thinking to the next deliverable.

On a flow or campaign work item, Draft a brief brings together the item, its parent brief, client details, dates, and linked SOPs and trainings. The result stays on the item. Use this brief lets a person compare it with the existing notes and choose Replace or Add below.

A QA check can start from a button or a configured stage move. It checks the work against the agency’s guidance, with optional pasted copy and read-only Klaviyo campaign or flow details. Findings stay with the item; a QA found issues mark calls for a person’s attention. A check is assistance, not a guarantee that the work is ready to send.

Useful context. Deliberate boundaries.

The agency sets up the jobs.

Admins choose the job, SOP, schedule or trigger, and recipients. Scheduled and work-item jobs use the agency’s chosen provider and model, with daily, weekly, and monthly spending caps.

People keep their access.

Team meetings and 1:1 context are opt-in. A 1:1 is limited to its two participants, and Homi receives its summary and action items, never its transcript. Private notebooks and review answers stay outside Homi.

A few useful distinctions

Does Homi send reports to our clients?

No. House prepares the report draft. A person reviews it and sends it to the brand. Handover bundles and recovery plans are internal drafts too.

Does connecting Klaviyo let Homi change a campaign?

No. The Klaviyo connection is read-only. It supplies reporting results and, when enabled for QA, details about the linked campaign or flow.

Does Homi read every channel and document?

No. It uses the sources and permissions supported in House. Reading Slack client channels and linked Google Drive copy documents is not available yet.

Homi, in the whole House

More room for the person behind the work.

The context makes Homi useful. Your team’s taste, care, and judgment make the work worth doing.

A useful draft needs something to draw on. Published SOPs and trainings give Homi the agency’s way of working.

Follow the knowledge into the work

Keep exploring

The next connection.

Back to the whole House See pricing