A designer selecting brass hardware and stone and oak samples over architectural floor plans on a sunlit studio table

Product

Design decision documentation software that does not depend on remembering.

Every decision is a future dispute waiting to happen. Archen documents it as it is made, not when you find time.

The problem

Documentation is the first thing to go when you get slammed.

Everyone documents decisions in the calm weeks. Then three projects hit deadline at once and the logging stops. The busiest stretch, the one with the most decisions, is the one with no record.

That gap is exactly where disputes live.

The client dispute that surfaces six months later traces back to the three-week stretch when the logging stopped.

A week of a designer working: Monday decision logged, Tuesday approval noted, then Wednesday, Thursday, and Friday left unchecked as the studio gets busy and the logging quietly stops

The solution

Archen documents the decision from the conversation around it.

The choice was made in an email, a reply, a recap. Archen reads it there and records what was decided, when, and by whom.

Even in your busiest weeks you still send those emails. You just stop logging them. Archen never needed you to log anything, so a slammed week is documented like a calm one.

An email reply "Let us go with the ribbed glass pendants over the dining table" is read by Archen and recorded as a dated decision: Ribbed glass pendants, dining, by Greta Sandoval, captured in both a calm week and a slammed week

Complete

A complete record, not a hopeful one.

Manual documentation is only as complete as your worst week. Here is what that looks like over a real quarter: logged by hand, next to captured by Archen.

A record completeness chart over the last 12 weeks: logged by hand reaches only 54 percent and dips in the busiest weeks, while captured by Archen holds at 100 percent every week with no gaps

What to document

Know what to document, then stop doing it by hand.

There are a handful of decision types worth capturing on every project: selections, approvals, scope changes, and the reasons behind them. Archen captures them from the communication where they happen.

The four decision types Archen captures automatically from communication: selections (what was chosen), approvals (what was signed off), scope changes (what changed), and rationale (why the decision was made), each pulled from the thread with no manual work

Founding 50

You are invited to help shape what comes next.

Fifty founding firms. A direct line to the team, a real say in the roadmap, and the first look at everything new, the self-updating client portal included.

Fifty seats. Applications are open now.

50 founding firms · Direct access to the team · A voice in what we build next