What is this page?
You received a link to a professional software proposal. It contains the project scope, requirements, pricing, timeline, and terms for the work being offered. You can review everything, ask questions, and respond — all from the same link. No account or app download is needed.Actions you can take
When you open the proposal, you have three options:Accept the proposal
Click Accept to approve the scope, pricing, and terms. You’ll be asked to provide:- Your full name (for the acceptance record)
- A visual signature (draw or type)
- Confirmation that you agree to the terms
Reject the proposal
Click Reject if the proposal doesn’t meet your needs. You can optionally include a reason, which helps the provider understand what didn’t work.Request a revision
Click Request Revision if you’d like changes before accepting. Include details about what you’d like adjusted — pricing, scope, timeline, or terms. The provider receives your feedback and can update the proposal. You’ll get a new notification when the revised version is ready.Proposal sections explained
Depending on the proposal type, you may see some or all of these sections:Requirements
The list of features, modules, or deliverables included in the project. Each requirement shows:- Name — what will be built
- Description — detailed explanation of the deliverable
- Complexity — estimated effort in story points (1 = trivial, 3 = small, 5 = medium, 8 = large)
- Priority — high, medium, or low
Price breakdown
The total cost and how it’s calculated:- Base cost — hours × hourly rate
- Modifiers — adjustments for tech stack complexity, urgency, or client discounts
- Taxes — if applicable
- Total — the final amount
Timeline
A visual timeline showing project phases, milestones, and estimated delivery dates. Each phase lists the requirements included and the expected duration.Milestones and payments
For milestone-based proposals, each deliverable has acceptance conditions and an associated payment. You pay when each milestone is completed and meets the defined criteria.Differentiators
A “Why choose us” section highlighting the provider’s relevant experience, technical skills, certifications, and past projects related to your needs.Governance and terms
Legal and operational terms that protect both parties:- Delivery conditions — what “done” means for each requirement
- Out of scope — what is explicitly excluded from this engagement
- Change management — how scope changes are handled and priced
- IP and code ownership — who owns the code after delivery
- Service commitments — response times, availability, and support terms
- Payment terms — schedule, methods, and late payment policy
Statement of Work (SOW)
Some proposals include a full SOW that consolidates all sections into a single reference document.Common terminology
If you’re not familiar with software project terms, here’s a quick reference:| Term | Meaning |
|---|---|
| Story points | A relative measure of effort. Higher points = more complex work. Common scale: 1, 3, 5, 8. |
| SOW | Statement of Work — a formal document describing the project scope, deliverables, timeline, and terms. |
| T&M | Time and Materials — a billing model where you pay for actual hours worked at an agreed rate. |
| Retainer | A fixed monthly fee for a reserved block of hours. Unused hours may or may not roll over. |
| Milestone | A defined deliverable with acceptance conditions. Payment is tied to completion. |
| Sprint | A fixed time period (usually 1-2 weeks) during which specific work is completed. |
| MVP | Minimum Viable Product — the smallest version of the product that delivers value and can be tested with real users. |
| API | Application Programming Interface — how different software systems communicate with each other. |
| Scope creep | When requirements grow beyond what was agreed, often without adjusting timeline or budget. |
Alignment questions
Some proposals include alignment questions — these are points the provider wants to confirm with you before starting. They might ask about:- Technical preferences (hosting provider, specific tools)
- Business priorities (which features matter most for launch)
- Timeline constraints (hard deadlines, dependencies on other projects)
- Access requirements (existing systems, accounts, credentials)
Chat with the provider
Every shared proposal includes a chat where you can message the provider directly. Use it to:- Ask questions about requirements or pricing
- Clarify technical details
- Discuss timeline adjustments
- Negotiate terms
Electronic signature
When you accept a proposal, Quikly records:- Your name and email
- A visual signature (drawn or typed)
- The exact date and time of acceptance
- Your IP address
- A SHA-256 hash of the document at the time of signing