Contracht executive brief
Code built. Not yet in production. No customer on this version.
Contents7 sections
01
What Contracht is
Contracht is software that keeps one record of a construction or improvement project, from the first scope through the final approval. Owners, property managers and contractors work from the same scope, agreement, change history, evidence and approvals. Where a project involves money, Contracht would prepare the information. An authorized financial provider would handle the money.
Each record may be fine on its own. Nothing connects what the parties agreed to what a person approved.
02
What exists today
The application code exists. This version has not yet run on a production database. No customer has used this version.
Built
- AI-assisted scope drafts
- Itemized proposals and side-by-side comparison
- Two-party agreement sign-off
- Material requests and owner approvals
- Photos and messages attached to each job
- Job-level approval with a project log
- Credentials labeled on file or verified by a person
Proposed, not built
- Change orders
- Milestones and milestone approvals
- Approval packages and completeness checks
- Payment-readiness status and provider hand-off
- A shareable property record and export
Earlier payment code remains in the codebase. The code is switched off and is not connected to any payment account. Contracht would not use the code without legal review and an authorized financial provider.
03
Where authorized financial providers may fit
The software coordinates. Authorized institutions control funds.
Contracht
Agreements · Evidence · Approvals · Instructions · Status · Project log
The record stops here.
Authorized financial provider
Financial accounts · Custody where authorized · Payment execution · Applicable financial compliance
Proposed role. No provider signed.
The viable model depends on the transaction type, the provider’s authority and legal review.
- Model A: Owner-funded contractor work
- The owner pays from its own money. Contracht could coordinate the record. An authorized financial provider could handle the payment.
- Model B: Lender-financed construction
- A lender finances approved work. Contracht could coordinate draw requests and evidence. The lender keeps disbursement control.
Both models are conceptual. Neither is an established service. Neither has had legal review.
04
From agreement to payment readiness
- Built
- Partly built
- Proposed
Built means the code exists. This version has not run in production.
01Partly built
Define
The needed work becomes a structured scope.
02Built
Agree
Itemized proposals become signed terms.
03Partly built
Document
Evidence and change orders attach to the agreement.
04Proposed
Verify
A qualified person would verify the evidence. Software would flag what is missing.
05Partly built
Authorize
An authorized person approves the work against the agreement.
06Partly built
Record
The record stays with the project and the property.
Software and people, stage by stage
- Define
- Software: AI prepares a draft from a plain-language request.
- People: An authorized person confirms the scope.
- AI scope drafts and work items are built. Milestones are proposed.
- Agree
- Software: Shows itemized proposals side by side against the same scope.
- People: An authorized owner or manager selects a proposal and signs.
- Itemized proposals, comparison and two-party sign-off are built.
- Document
- Software: Files each item against the job and the agreement.
- People: The contractor supplies evidence. The owner approves changes.
- Photos, messages and material approvals are built. Change orders and document evidence are proposed.
- Verify
- Software: Would check completeness and flag inconsistencies. Nothing more.
- People: Qualified people judge workmanship, safety, legal compliance and financial eligibility.
- Proposed. Not built.
- Authorize
- Software: Records the decision. Could prepare the information for a provider.
- People: An authorized person approves. The financial provider controls any payment, under an arrangement not yet designed.
- Job-level approval and its log entry are built. Milestone approval, approval by agreement version and provider hand-off are proposed.
- Record
- Software: Keeps the project log and controls who can see it.
- People: Owners decide who gets access.
- The project log is built. A shareable property record and export are proposed.
05
What we still need to test
- Which transaction type is the right place to start.
- Whether either funding model works legally, and under whose authority.
- Whether signed records in this form meet what parties and lenders need.
- Whether operators will use Contracht on real work, and what they would pay for.
- Whether contractors will supply evidence in Contracht.
06
Proposed pilot
One property-improvement project, with one property operator and one contractor. A complete agreement and approval record. Contracht handles no money.
Success criteria
- The record holds all key project documents
- Each decision traces to an authorized person
- The pilot measures administrative effort
- Real users accept the workflow
- The parties understand legal and financial viability
If a financial provider participates, the parties set its role and approvals separately.
07
Contact and downloads
Jason Murphy, Founder
jasonmatthewmurphy@gmail.com216.367.9131
Preliminary business discussion. Not an offer of any financial service. Contracht is not a bank, title insurer, surety, payment processor or escrow provider.