Skip to main content

​
Marcos — senior fullstack freelancer

The situation: Marcos is a senior fullstack developer in Buenos Aires. He gets 3–4 project inquiries per week via email and LinkedIn. Each proposal used to take him 3–4 hours in Google Docs — scoping requirements, researching rates, writing terms, formatting the document, and manually calculating totals. How he uses Quikly:
  1. A client emails a brief for an e-commerce platform with authentication, product catalog, and Stripe payments.
  2. Marcos pastes the email into Quikly and clicks Analyze with Quimy.
  3. Quimy scores the brief (7/10), flags missing details (payment flow edge cases, hosting preferences), and generates 14 requirements with story points and hour estimates.
  4. Marcos adjusts two complexity scores, bumps the hourly rate to match the client’s enterprise profile, and enables the risk analysis section.
  5. He clicks Share, copies the link, and sends it via email.
Result: The entire process takes 15 minutes. The client receives a professional document with branded scope, delivery conditions, out-of-scope definitions, and electronic signature — not a Google Doc with a price at the bottom. What changed: Marcos now responds to inquiries the same day. His close rate improved because clients see a structured, professional proposal that answers their questions before they ask.

​
Laura — UX designer and consultant

The situation: Laura runs a one-person UX consultancy in Madrid. She works with startups and mid-size companies on UX audits, design systems, and product redesigns. Her challenge isn’t writing scope — it’s pricing. She never knows if she’s charging too much or too little compared to the market. How she uses Quikly:
  1. Laura uses the Rate Calculator at app.getquikly.com/rate-calculator to benchmark her rates. She enters her role (UX Designer), seniority (Senior), region (Spain), and client industry (Fintech). Quimy shows her where she falls in the market distribution.
  2. For each project, she starts from a saved template — “UX Audit — Retainer” — that includes her standard retainer terms, monthly hours, SLA, and custom clauses for design deliverable ownership.
  3. She pastes the project brief, Quimy generates the scope, and she adjusts the monthly hours and deliverables.
  4. She shares the proposal link. The client reviews the retainer terms, asks Quimy to explain the revision policy, and accepts with an electronic signature.
Result: Laura stopped guessing her rates. She increased her hourly rate by 15% after seeing she was consistently below the market median for her profile. Templates cut her proposal creation time from 2 hours to 20 minutes. What changed: Confidence in pricing and a professional, repeatable process that doesn’t depend on copying and modifying old Google Docs.

​
DevStudio — 12-person dev shop

The situation: DevStudio is a development agency in Mexico City with 12 engineers. They compete for enterprise contracts against larger consultancies. Their proposals used to be informal — a shared doc with a rough scope and a total at the bottom. They lost deals because their proposals didn’t convey the rigor clients expected at the 50K–50K–150K level. How they use Quikly:
  1. The sales lead creates a Staff Augmentation proposal for a fintech client that needs a dedicated team for a 6-month platform rebuild.
  2. She defines three phases in the proposal:
    • Phase 1 — Discovery & architecture (3 weeks): Tech Lead at 100%, Senior Backend Dev at 50%.
    • Phase 2 — Core build (16 weeks): Full team — Tech Lead, 2 Senior Devs, QA Engineer, DevOps.
    • Phase 3 — Stabilization & handover (3 weeks): Tech Lead, QA, DevOps.
  3. Rates come from DevStudio’s rate card with a 25% agency margin (invisible to the client). Quimy generates SLA terms, IP clauses, replacement policy, and ramp-up/ramp-down conditions.
  4. The client receives a proposal that looks like it came from a Big 4 consultancy — phased team allocation, per-role rates, governance terms, and e-signature.
Result: DevStudio won the contract. The client told them the proposal was the most professional they’d received from a shop their size. The entire proposal took 45 minutes to build. What changed: DevStudio standardized their proposal process across the whole team. Anyone on the sales side can generate a proposal using the rate card and templates — they don’t need a senior engineer to scope every deal.

​
Ana — marketing technology consultant

The situation: Ana consults for marketing agencies on their tech stack — CRM integrations, analytics pipelines, and automation workflows. Her typical engagement is a 6-month retainer with a fixed monthly budget. The challenge: clients always try to add “one more integration” outside the original scope, and without clear boundaries, she ends up doing unpaid work. How she uses Quikly:
  1. Ana creates a Retainer proposal for a marketing agency that needs ongoing CRM and analytics support.
  2. She sets 40 hours/month at a discounted retainer rate, 6-month minimum commitment, and 20% rollover for unused hours.
  3. Quimy generates the governance section: hour reporting cadence (biweekly), request process (tickets via email, 24h response time), prioritization rules, and an explicit change request process for out-of-scope work.
  4. The risk analysis flags “scope ambiguity in analytics reporting” and suggests adding a definition of which reports are included vs. custom.
  5. Ana adds a custom clause: any integration not listed in the scope requires a separate estimate and approval before work begins.
  6. She shares the proposal. The client reads the retainer terms, asks Quimy to clarify the rollover policy, negotiates the minimum commitment down to 4 months, and accepts.
Result: Three months in, the client asked for a new integration outside the scope. Ana pointed to the clause in the signed proposal. The client approved a separate estimate without friction — the boundary was clear from day one. What changed: Ana stopped losing hours to scope creep. The signed proposal with explicit governance terms became her contract, not just a price quote. When boundaries are in writing and signed, the conversation shifts from “can you just add this?” to “let’s scope this properly.”