Client request
NO
Northstar LabsToday · 10:42
“Could we add single sign-on and a separate admin role before launch?”
Outside the signed authentication and permissions scope
Censiq for independent developers
Price every before it enters the sprint.
Keep your development margin by pricing changes before the sprint.
A new integration, user role, migration, or edge case should not enter the sprint as a casual message. Censiq helps you price and approve the change first, then carry deposits, milestones, support retainers, and follow-up through to payment.
Free setup · No credit card required
Northstar Labs / Agreement
Engagements Northstar Labs
Build agreement · AGR-024
SignedSaaS MVP development
Prepared for Northstar Labs
- Agreement value
- $12,000 USD
- Delivery target
- Production release
- Feature boundary
- Written and signed
Build scope
Authentication, billing, admin workspace, production launch, and a 30-day handoff period.
Payment milestoneAmount · USD
- 01
Project depositDue on signature
$3,600 - 02
Core product buildDue at staging approval
$4,800 - 03
Launch and handoffDue at production release
$3,600
Client signature recordedPrivate review link
Change order · CO-001Approved
Single sign-on and admin role
+$1,800+7 days
Client approval recorded
The full value of the work
$12,000 + $1,800$13,800 USD
- 01Added features priced before the sprint
- 02Milestones ready when they become billable
- 03Support limits written into the signed agreement
- Censiq handles
- Signed scope, invoice drafts, changes, and follow-up
- Your client gets
- Private review links—no Censiq account required
- Your money goes
- Directly to your bank account
Where signed work loses value
The work changes in chat. Your fee and deadline usually do not.
Development projects lose margin when commercial decisions live in messages while the original agreement and invoice schedule stay unchanged.
01
What usually happens
The “small change” becomes another sprint.
A new integration, role, migration, or edge case enters the backlog without a written price or delivery extension.
With Censiq
Turn the request into a signed change order with the added scope, fee, and timeline impact before implementation starts.
02
What usually happens
A milestone ships before the invoice is ready.
The technical trigger happened, but billing still depends on recreating amounts and terms from an old document.
With Censiq
Carry every agreed milestone into a connected invoice draft, ready for your review when the event becomes billable.
03
What usually happens
Post-launch help becomes unlimited support.
Fixes, monitoring, calls, and new requests blend together after handoff while recurring billing relies on memory.
With Censiq
Define maintenance coverage, limits, response windows, and recurring invoice drafts as a separate retainer.
The commercial record in motion
From signed build scope to confirmed bank transfer
Each step carries forward the client, deliverable, amount, currency, and approval that made the work billable.
Define the build
Record deliverables, exclusions, milestones, and the boundary between a defect and new scope.
Same client, scope, amount, and approval context.Sign and fund kickoff
The client signs through a private link and the agreed deposit is ready to invoice.
Same client, scope, amount, and approval context.Bill each milestone
Review and send the connected draft when staging, launch, or handoff becomes billable.
Same client, scope, amount, and approval context.Approve changes first
Price additional work and record its delivery impact before another ticket enters the sprint.
Same client, scope, amount, and approval context.Follow up and close
Send reminders, verify the direct transfer, confirm payment, and issue the receipt.
Same client, scope, amount, and approval context.One engagement. Every commercial decision.01 / 05
Northstar Labs / Agreement
Illustrative client recordReady to send
Build agreement · AGR-024
SaaS MVP development
Deliverables, exclusions, acceptance, and release milestones
Build scope
Authentication, billing, admin workspace, production launch, and a 30-day handoff period.
Feature boundary
New features require an approved change order.
01
Project deposit
$3,60002
Core product build
$4,80003
Launch and handoff
$3,600Agreement total$12,000 USD
Illustrative workflow · No account required to explore
Built for independent developers
Bill the way development work actually happens.
Give deposits, build approvals, launch, and ongoing support their own clear commercial rules instead of forcing every engagement into one final invoice.
01
Deposits before development begins
Make the start condition explicit and give the client one professional payment request tied to the signed scope.
Example: 30% on signature before repository setup and sprint planning.Payment schedule$12,000 USD
01
Project depositDue on signature
$3,60002
Core product buildDue at staging approval
$4,80003
Launch and handoffDue at production release
$3,60002
Milestones clients can verify
Connect invoices to observable delivery points instead of vague percentages of completion.
Example: staging approval, production release, and final handoff.New client request
Change order · Approved
Single sign-on and admin role
+$1,800+7 days
Work can proceed
03
Maintenance retainers
Keep post-launch support terms separate from the build and make the recurring amount and response window clear.
Example: $1,500 monthly for monitoring, fixes, and a defined support allowance. Invoice sentDay 0
Reminder in contextDue date
Payment verifiedReceipt issued
Go deeper on one commercial problem
Practical controls for independent developers.
Use a focused workflow or start with a copy-ready commercial structure for the work in front of you.
010203
Invoice milestones for developers
Copy a payment schedule with a worked development example, clear invoice triggers and client review deadlines.
Change orders
Price added features and show their delivery impact before building them.
Maintenance retainers
Define post-launch coverage, response windows, limits, and recurring billing.
Fits the way you already work
Your delivery tools stay. Censiq connects the commercial decisions.
01
Your delivery tools
Do the specialist work where it belongs.
Keep GitHub, Linear, Jira, or your preferred delivery tools for issues, code, and releases. Your client does not need another engineering workspace to understand what they signed and what they owe.02
Censiq
Keep one connected commercial record.
Use Censiq for the agreement, payment milestones, invoices, direct bank-transfer details, reminders, confirmation, receipts, and revenue record connected to the engagement.03
Your client
Review, sign, and respond without onboarding.
Clients use secure private links to review agreements, sign, view invoices, report a bank transfer, and receive a receipt. They do not need a Censiq account.Before you start
Clear answers before you move client work.
Client access, existing tools, direct payments, and what happens after signature.
Does Censiq replace GitHub, Linear, or Jira?
No. Keep code, issues, releases, and technical delivery in the tools your team already uses. Censiq manages the client-facing commercial record: signed scope, milestone billing, approved changes, retainers, payment follow-up, and receipts.
How does a signed milestone become an invoice?
When the client signs a milestone-backed agreement, Censiq creates one connected invoice draft for each milestone. You review the amount, due date, payment details, and billing trigger before sending it when that stage becomes billable.
Does my client need a Censiq account?
No. Your client receives secure private links to review and sign the agreement, view an invoice, report a transfer, and receive a receipt. They do not need to create a workspace or remember a password.
Does Censiq process or hold the client’s payment?
No. The invoice displays your bank-transfer instructions and the client pays your account directly. Censiq helps track the invoice and confirmation workflow; your bank or an intermediary bank may still charge transfer or conversion fees.
Censiq for independent developers
Give the next build a signed path from added scope to payment.
Start with a signed scope, price additional features before they enter the sprint, and move each approved milestone toward payment.
Start freeNo credit card required