Proposal and invoice tool for developers
Scope creep is a change request you forgot to price
Scope and acceptance criteria written once, priced once, approved once. The deposit is paid at approval, by card or bank transfer, and when the client accepts the build the balance is paid on the same page.
Get started freeThe problem
Sound familiar?
The ballpark in Slack becomes the contract
A client describes the project in a thread and wants a number. You type a range, they hear the bottom of it, and you build to a figure typed in thirty seconds with nothing written down.
'Can you also add' after every demo
You demo the feature. They love it. Then: can it also do roles, a dashboard, an export. Each is a day. With no written line between a bug fix and a new feature, every addition is argued afterwards, not priced first.
Shipped on Friday, invoiced some time in May
The final deploy goes out, you close the editor and the invoice waits for a quiet moment that never comes. Their 30 day term starts when finance receives it, not when you shipped.
The solution
How VytDeal helps
One scope, deposit and balance on one page
Write the scope and acceptance criteria once. Set the deposit at any share, 30 percent by default; many developers ask for more on a fixed price build. Paid on approval; the balance comes due on the same page at delivery.
Hour blocks once, maintenance on repeat
A once-off block of hours is a one-off line; a block sold monthly is a recurring package. A maintenance plan recurs monthly, quarterly or yearly, collected from a saved card or bank debit, or invoiced each period. On its own it starts at approval; behind the build it waits until you start it at hand-over, then runs until cancelled.
Change requests priced, approved and recorded
The accepted scope cannot be edited after approval, on purpose. A change request is its own deal page: written, priced, approved and recorded, so the original and every variation keep their own dated record.
GST on its own line, bank transfer for the big invoices
Created on approval, in AUD, with GST at 10 percent or any rate on its own line, and no ABN printed: put yours in the terms. Card payments land in your own Stripe account; for a larger invoice offer bank transfer, BPAY or PayID.
How it works
Three steps to getting paid
Scope it after the call
Write what is in, what is out, and what acceptance looks like. Add your terms, including IP passing on final payment and the defect window. Set the deposit, GST and expiry.
Send the link instead of the doc
The client reads it without an account, approves, and pays the deposit on the same page.
Build, hand over, collect
The page shows you when it was opened. Once the client accepts the build against the criteria, mark it delivered; the balance comes due on the same link. Start the maintenance plan that day.
FAQ
Frequently asked questions
Can I invoice milestones against one scope, or only a deposit and a balance?
A deposit and a balance on one page. Set the deposit to what the first stage is worth; the balance comes due when you mark the work delivered. No chain of milestone invoices: a third stage gets its own deal page when you reach it.
Can a monthly retainer or a block of hours run alongside a project?
Yes, on one page: the build as one-off lines, the retainer as a recurring package. The client saves a card or bank debit on approval; nothing is charged until you start the retainer after the build is delivered. A prepaid block of hours is a one-off line.
Does my own contract attach: IP on final payment, acceptance criteria, warranty window?
Its clauses do: IP assigning on final payment, the acceptance criteria and the defect window go in the terms, and the client must tick them to approve. The dated record keeps them complete, so what counts as accepted is settled from the page. The client confirms with a code from their own inbox if you require it on the deal. Not a contract or an e-signature, no legal advice; your contract still sits alongside.
Can the client pay by bank transfer or direct debit on a large invoice?
Bank transfer, BPAY and PayID can be offered on any deal alongside card; the client marks the transfer made and you confirm it. A retainer can be collected by bank debit from the mandate saved at approval.
What counts as a bug fix and what is a new feature?
Whatever your terms say, which is why they go on the page. Name the defect window and what it covers. Anything outside it is a change request: price it as its own deal page and get it approved before you build.
Related
Ready to close deals faster?
Create your first deal page in minutes. No credit card required.
Get started free