Claybar Family Companies · Practical AI

Capture the arrangement once. Everything else follows.

An arrangement conference becomes clean, structured case data — the Personal History filled, the obituary drafted, the memorialization planned — so your directors can be present with the family instead of buried in paperwork.

Built on
substrate.exe — one engine, on-prem
Your data
never leaves the box
System of record
Kindred — written, not replaced
Prepared by
Horizen IT Services
The insight

One capture, fanned out to every form

First Call and Personal History are the same data model captured at two moments. Capture it cleanly once, at the source, and it propagates — to the forms, to the obituary, to Kindred. The leverage isn't fixing paperwork downstream; it's never re-typing it.

Arrangement
the conversation, as it happens
Claybar
structures it against your forms
Director review
confirm — nothing writes without you
Kindred & every form
auto-populated
Live, end to end

A real arrangement, processed in seconds

This ran on the engine — a sample arrangement transcript in, a complete case out. No template, no re-typing. The model fills only what the family stated, and flags what they didn't — look at the flags below: the family never gave a Social Security number, never stated his mother's name, and the engine refuses to guess.

claybar · chain/claybar_arrangement · extract → obituary → memorialize · 3/3 steps · live
Input — the arrangement transcript
Director: Can we start with his full legal name? Daughter (Margaret): My father was Robert James Ellison. Everyone called him Bob. Director: When was he born, and when did he pass? Margaret: March 2nd, 1941, in Akron, Ohio. He passed last Tuesday, June 3rd, at Mercy General. Margaret: He'd been at 418 Maple Street, Springfield, forty years. Widowed — my mother Helen passed in 2019, her maiden name was Carver. His father was Walter Ellison. Three of us — me, Thomas, and Anne. Margaret: He was a machinist at Springfield Tool & Die, thirty-five years. Springfield High, class of '59. Margaret: Army — a Corporal, 1961 to 1964. Methodist; we'd like Reverend Hollis to officiate. Margaret: Burial, next to Mom at Oak Hill. A traditional service that Saturday. He loved his garden — roses on the casket if we can. Margaret: List me as informant — Margaret Ellison, his daughter, cell 555-0142.
Personal History — auto-filled

Robert James Ellison

Date of birth1941-03-02 · Akron, OH
Date of death2026-06-03 · Mercy General
Residence418 Maple St, Springfield
SpouseHelen (née Carver) · d. 2019
FatherWalter Ellison
Motherflagged — not stated
OccupationMachinist · Springfield Tool & Die · 35 yrs
EducationSpringfield High · class of 1959
MilitaryArmy · Corporal · 1961–1964
FaithMethodist · Rev. Hollis
DispositionBurial · Oak Hill, beside his wife
SurvivorsMargaret, Thomas, Anne
InformantMargaret Ellison · daughter · 555-0142
SSNflagged — not stated
Raceflagged — not stated
Obituary — drafted in the house voice

Robert James Ellison, 85, of Springfield, passed away on June 3, 2026, at Mercy General Hospital. Born March 2, 1941, in Akron, Ohio, the son of Walter Ellison, Robert was a graduate of Springfield High School, class of 1959. Robert proudly served in the United States Army from 1961 to 1964, achieving the rank of Corporal. He then built a thirty-five-year career as a machinist with Springfield Tool & Die, and made his home on Maple Street, where he was a faithful member of the Methodist church and tended a garden he dearly loved. Preceded in death by his beloved wife, Helen (Carver) Ellison, in 2019, he is survived by his children Margaret, Thomas, and Anne, who will cherish his memory. A traditional service will be held this Saturday with Reverend Hollis officiating. Robert will be laid to rest at Oak Hill Cemetery beside his wife. The family has requested roses on the casket.

Memorialization — recommended from his life, never upsold
Essential
Military funeral honors & flag presentation
Army Corporal, 1961–1964 — an earned tribute to his service.
Essential
Rose spray for the casket
The family specifically requested roses — he loved his garden.
Recommended
Veteran memorial marker with military insignia
As an Army veteran, he is entitled to a government-provided marker.
Premium
Engraved plaque with a machinist-tools motif
Thirty-five years at Springfield Tool & Die — a tribute to his craft.

Every field, line, and recommendation above was produced by the engine from the transcript — grounded only in what the family said. Where the family didn't state a fact (his mother's name, the SSN), the engine flags it for the director instead of guessing. A director reviews and confirms before anything is written to Kindred.

Try it — right now, on this page

Run an arrangement through the live engine

This is not a video or a mock-up. The button below sends the transcript to the engine and runs the same three-stage pipeline — extraction, obituary, memorialization — live, in about half a minute. Edit the sample, or paste a de-identified conference of your own.

claybar · live engine · POST /api/v1/forge/claybar
Your transcript
Personal History — auto-filled

Obituary — drafted in the house voice

Memorialization — recommended from the record
Why this, why us

One binary. Not a stack to babysit.

Built in, not bolted on

Compliance is the engine

Role-based access, per-family isolation, a full audit trail, and a human gate on every write to Kindred — one consistent plane in one on-prem binary, not four cloud services to wire and keep in sync.

The data stays home

PII never leaves the box

Capture, extraction, and drafting run in-process on your own hardware. The only outside system is Kindred — your system of record — written to, never replaced.

Days, not months

Capture-once is the payoff

The arrangement, captured cleanly once, fans out to the First Call, the Personal History, and the Preneed view with no re-typing. The duplicate entry that slows preneed filing originates at the table — so we end it at the table.

Start small, it carries

Prove it on your own forms

A proof of concept runs on Claybar's actual forms with de-identified samples — no Kindred access required — and credits forward when you proceed to the full write-back.

How it lands

Four steps. Each one safe to stop at.

Nothing about your operation is bet on day one. Claybar runs alongside what you have, earns trust per workflow, and Kindred stays your system of record throughout.

1 · Mirror
read-only alongside today's process — zero workflow risk
2 · Assist
this demo, on your forms — directors review every field
3 · Write-back
one workflow at a time, each behind a director's confirm
4 · Full flow
capture once, everywhere — Kindred in lockstep