WYEA / How we work
How we work
One week to a working prototype, then a fixed price for the build
Every engagement starts the same way: a conversation, an NDA, and software your attorneys can try on a live matter inside the first week. Nothing larger is quoted until your firm has used something real.
The first month
White-glove, from first meeting to every update
Both principals are in the room for all of it. There is no account manager between your firm and the people writing the code.
-
01
We sit with your attorneys
In your office, following one piece of work end to end: who touches what, and where the hours go.
-
02
Prototype in one week
Built against your real documents, under NDA, and put in front of the people who will use it rather than the ones who bought it.
-
03
Scoped in writing
If the prototype earns it, the full build is quoted at a fixed price with the deliverables and dates written down first.
-
04
Deployed your way
Cloud, your own cloud account, or your own hardware, with the isolation and audit trail built in from the first commit.
How the engagement is shaped
Three commitments that decide everything else
The way the work is priced and staffed is the reason the rest of it holds.
Priced before it starts
Your firm knows the number before any work begins, at every stage, including the first one.
Fixed, not hourly
A price for the work, agreed in advance. You will never see an open-ended hourly bill for exploratory work.
Per engagement, not per seat
One price for the system your firm asked for. Hiring three associates does not change what you pay.
Scoped in writing
Deliverables and dates are written down and signed before any build work begins.
Staffed by the people who build it
The firm is two engineers, and both are on your engagement from the first meeting to the last release.
No handoffs
Nobody who was not in the room when your workflow was explained will be the one writing the code for it.
No support tier
When something breaks you write to the person who wrote it, so answers come back in minutes, not after a relay.
Training by the builders
Sessions run in your office by the engineers, repeated for new staff without a separate charge.
Owned by your firm
What is delivered is a system your firm holds, and the exit terms are settled before anything is built.
Your data, outright
Documents, matter records, and the deployment belong to your firm, and export is in an open format.
Your environment
Managed single tenant, your cloud account, or your hardware. The isolation is identical in all three.
Terms up front
Code ownership and licensing are set in the engagement agreement, with the options in front of you first.
What each stage produces
Every stage ends with something your firm can hold
A deliverable, not a status update.
The terms
What every engagement holds to
These are commitments in the engagement agreement, not settings in a product.
What we ask of you
Three things, and not much of anyone's time
The engagement is designed around the fact that your attorneys are billing while we build.
A half day in your office
Once, at the start. We watch a matter move and ask questions, rather than sending a requirements questionnaire.
Real documents, under NDA
A prototype built on sample data proves nothing. We work from the files your firm actually handles.
One attorney who will try it
Someone who uses the prototype on a live matter and tells us plainly where it gets in the way.
What it costs
Quoted before the work, not billed after it
Pricing is per engagement, not per seat, so it does not change when your firm hires.
Every engagement starts with a fixed-price one-week prototype, quoted before we begin. You will never see an open-ended hourly bill for exploratory work. If the prototype earns it, we scope the full build the same way: fixed price, defined deliverables, dates in writing.
Questions partners ask
Before the first call
How long does the whole thing take?
A working prototype is in your attorneys' hands in the first week. A full build is scoped from there, and the scope is written down with dates before work starts, so the answer stops being an estimate.
What if the prototype does not convince us?
Then the engagement ends there, at the price that was quoted, and your documents are returned or destroyed on your instruction. That is the point of putting something real in front of your attorneys before anyone talks about a larger build.
Who trains our staff?
The two engineers who wrote the software. Training is part of the engagement, run in your office, and repeated for new staff without a separate charge.
What happens when something breaks?
You call or write to the people who built it. There is no support queue and no first-line tier, so answers come back in minutes and nothing is lost in relay. Meet the principals.
Do you work outside legal?
Yes. The platform is built around documents, versions and evidence rather than around one profession, and it runs in insurance as well as legal. If your people spend the day reading documents carefully and are held to what those documents actually say, the same machinery applies.
Start a conversation
Tell us what your people spend the day reading.
Thirty minutes, no obligation. If a shared product would serve you better, we will say so on the call.
The Brief
The week in legal, in four minutes.
Free, national to Orange County, every Wednesday.