What's live.
What's next.
What we're deliberately not building.

Clients approve the job, payment schedule, and payment method before you collect for the work.

• Clients authorize the full payment path before work begins
• Credit Card or Bank Transfer authorized with the agreed terms
• No work starts until the job is authorized

Agree named cost deposits with the client upfront. Collect each when it is due, without creating another invoice request.

• Collect material deposits before ordering starts
• The client approves the deposit schedule and payment method before collection
• Deposit status is tracked on the job

Collect the agreed payment without creating or sending another invoice first. Credit Card payment succeeds at phase start; Bank Transfer work starts after the transfer clears.

• Collect the agreed amount when each work phase starts
• The job never waits on a single final invoice
• Client review stays separate from Stripe bank payout timing

Unanswered work reviews auto-approve after 72 hours, subject to the job’s review rules. This closes the work review; it does not collect or release payment.

• Eligible work reviews auto-approve after 72 hours without a client response
• Closes a stalled review without controlling Stripe payout timing
• The countdown is visible to both sides

Collected payments belong to the contractor’s connected Stripe account. Stripe controls when available funds pay out to the contractor’s bank.

• Collected payments go to the contractor’s Stripe account
• Stripe controls availability and bank payout timing
• PhaseContract shows the payment and payout status without holding the contractor’s funds

Clients review the scope, deposits, work phases, change-order rules, and collection plan before authorizing the job.

• Clients see scope, deposits, phases, and change rules first
• The full collection plan is visible before authorizing
• Added work needs its own client approval

Let clients pay from a US bank account. Collect Smart Deposits, work-phase payments, and approved changes through the same shared job workspace.

• Clients connect and authorize their bank account before collection
• Work waits until the Bank Transfer clears; processing is not the same as paid
• Payment progress, failures, and refunds stay visible alongside the job record

Clients open the shared job workspace from email or text without creating another account first. Access stays tied to the job and its verification steps.

• Clients open the shared workspace from email or text
• No new account or password required to start reviewing
• Access stays tied to the job and its verification steps

Clients confirm job authorization and added-work approval with emailed one-time codes where those actions require verification.

• Emailed codes verify the required client action
• Codes are tied to the job and action being approved
• Agreed deposit and work-phase collection does not require a new client code each time

When a card issuer asks for extra confirmation, PhaseContract keeps the payment in the right retry or verification flow instead of treating it like a normal failure.

• Handles issuer step-up checks without dropping the payment
• Keeps the charge in the right retry or verification path
• A verification prompt is not treated as a hard failure

Describe the job in plain English and turn it into editable deposits, work phases, amounts, durations, and review checkpoints.

• Turn a plain-English description into a structured draft
• Deposits, phases, amounts, and checkpoints come back editable
• Adjust anything before the job is sent

Prefer to build the job yourself? Contractors can manually add and edit deposits, work phases, amounts, durations, and proof requirements before sending.

• Build the job by hand without using AI
• Add and order deposits and work phases yourself
• Set amounts, durations, and proof requirements per phase

Price added work in a change order and get the client’s approval before doing it. Its price, approval, payment, and proof stay with the job.

• Capture mid-job scope changes with photos and amounts
• The client approves the change before it counts
• Every change stays in the shared workspace history

Made a mistake? Edit job details, client info, and phases even after sending. Active jobs have limited editing to protect financial terms.

• Fix job details, client info, and phases after sending
• Active jobs limit edits that touch financial terms
• Changes stay in the auditable shared workspace history

Start structuring a job and save it without sending. Come back later to add client details and send when ready.

• Structure a job and save it without sending
• Come back to add client details later
• Draft jobs are free

Pause a job when work needs to stop, then resume it when the job is ready to continue. The shared workspace keeps the pause and remaining work visible.

• Pause a job when work stops, resume when it restarts
• The paused state and next due work stay visible
• No need to rebuild the job

One place for the owner, assigned foreman, and client to see the agreed work, payment progress, and what happens next.

• Scope, deposits, work phases, changes, and proof stay with the same job
• Each person sees the information and actions their role allows
• Clients return through their workspace link without creating an account

Photos, files, notes, and required evidence stay attached to the exact work phase the client is reviewing.

• Photos, files, and notes attach to the exact phase under review
• Required evidence travels with the work, not a separate folder
• Proof stays part of the payment record

Clients review submitted work and its proof, approve it, or request changes within the review window.

• Clients approve, request changes, or let it auto-approve
• Reminders nudge a stalled review
• Stripe handles bank payout timing for direct payments after collection succeeds or bank payments clear

Each successful collection creates a receipt against the approved job and work phase, reducing the manual invoice chasing and reconciliation that usually follow project payments.

• Receipts are tied to the client, job, and exact deposit or work phase
• Contractors can download the payment record without building another invoice by hand
• Payment status and receipt history stay visible in the shared workspace

Keep the agreed look and details beside the work. Add reference photos and notes to the phase they belong to, so the crew and client have the same starting point.

• Group reference material by topic within each work phase
• References stay visible in the proposal and shared job workspace
• Keep planning references separate from proof of completed work

Built for contractors on the go. Create jobs, start work phases, upload proof, and handle client decisions from a phone.

• Create jobs, start phases, and upload proof from a phone
• Built for contractors working on the jobsite
• The same workflow scales up to desktop

Clients can request cancellation under the agreed response windows. Owners can close remaining work directly, with a finish-or-refund decision for a collected unfinished phase.

• Client cancellation requests follow the job’s agreed response rules
• Owner closeout cancels future uncollected work
• A collected unfinished work phase must be finished or refunded

You stand behind your work. We’re proud to recognize it. An earned verification badge puts your business’s reviewed reputation on your proposal and in the shared workspace.

• Request a review of your business identity, public reputation, and supporting credentials
• Clients can open the badge to see the review date and individual results
• A dated business review, not insurance or a guarantee of the work

Keep the job moving while you run the business. The active assigned primary foreman can collect due deposits, start work-phase collection, upload proof, and draft field changes. The owner keeps company controls and reviews actions that require owner approval.

• Assign a foreman to the jobsite workflow
• Assigned foremen can collect due deposits and work phases without separate owner approval
• Owner review applies to proposal sends, job pauses, cancellation, and field change requests