Before You Share

Check link access settings
The most common roadblock is a locked or restricted file. Before sending, make sure your Figma link is viewable without requiring us to request permission. “Can view” is usually enough—we don’t need edit rights at this stage. This prevents delays and ensures our team can dive right into reviewing your layouts.

Practice simple file hygiene
A well-organized file saves hours of guesswork. You don’t need to clean every pixel, but a little tidying goes a long way. Label your pages with clear names like Homepage, Dashboard, or Onboarding Flow rather than generic terms. Remove outdated drafts or move them into a clearly marked archive section. When layers, frames, and artboards follow a logical order, we can quickly map your design against the scope you want quoted.

---

Scope Snapshot

To give you a solid quote, we don’t need perfection—we just need a snapshot of the essentials. Here’s what helps us build an accurate estimate:

• Page list
  A simple inventory of the pages or views in your file. Even a quick outline helps us see the project’s size.
  
• Special layouts
  Flag any screens that break the usual structure, like dashboards, multi-step forms, or interactive maps. These tend to influence effort more than standard pages.
  
• States
  Show variations like hover, active, disabled, or error states. If they’re not designed, a written note (“buttons will have hover states”) is enough.
  
• Animations in words
  You don’t need polished prototypes. A short text description like “fade in on load” or “slide transition between steps” is perfect.
  
• Content readiness
  Let us know if the content in your designs is final, placeholder, or still in development. This affects how much flexibility we should assume in the build.
  
• Copy length ranges
  Tell us if text blocks may expand significantly, such as product descriptions or multilingual headings. Short versus long copy can impact layout adjustments.
  
• Languages
  If the project needs to support multiple languages, even if translation isn’t ready, flag it now. This helps us factor in layout considerations like right-to-left scripts.
  

---

What We Don’t Need Yet

To keep the quoting stage fast and focused, you can hold off on details that matter only after kickoff:

• No credentials
  We don’t need logins, admin access, or third-party account details yet. Keep those safe until we’re in development mode.
  
• No hosting access
  Server, domain, or platform credentials aren’t relevant for estimating. We’ll request them later if needed.
  
• No plugin lists
  Figma plugin usage doesn’t usually change the scope estimate. What matters is the output—the designs themselves—not the tools used to create them.
  

---

How We Estimate in Under 12 Hours

We follow a streamlined process designed to get you a quick, dependable answer:

1. File review
   We scan through your Figma link, noting page count, unique layouts, and any complexity markers.
   
2. Scope assumptions
   Where details are missing, we make reasonable assumptions based on industry standards. For example, if no button states are shown, we assume typical hover and active versions.
   
3. Complexity markers
   We highlight items like animations, conditional flows, or large content blocks that may influence effort.
   
4. Estimate draft
   Using the scope snapshot, we prepare a phase-based timeline and effort outline, balancing what’s clear with what’s assumed.
   
5. Internal check
   Another team member reviews the draft to make sure the scope is consistent and assumptions are noted.
   

This conceptual approach lets us return a thoughtful quote within 12 hours, while leaving room for refinement once the project kicks off.

---

After You Submit

Once you’ve shared your link and we’ve turned around a scope estimate, here’s what usually happens next:

• Clarifying questions
  If anything is ambiguous, we’ll send a short list of questions rather than making broad guesses.
  
• Timeline by phases
  We outline the project in manageable stages, such as design handoff, development, and final review.
  
• Deposit
  Before starting, we typically secure a deposit to confirm your spot in the production schedule. Exact details will be shared once you’re ready.
  

These steps keep the process transparent while ensuring you have a clear roadmap for what comes next.

---

FAQ

1. Do I need to share every draft page?
No. Only share the pages relevant to your current project scope. Old experiments or unrelated drafts can stay hidden or archived.

2. What if my designs aren’t finished?
That’s fine. As long as the main structure is visible, we can still provide a reliable estimate. Just flag which areas are still in progress.

3. Can I send a PDF export instead of a link?
We recommend a live Figma link, since it allows us to inspect layers and better understand layouts. PDFs are harder to assess quickly.

4. What if my file contains sensitive data?
Replace any confidential text or imagery with placeholders before sharing. We don’t need real data to scope effort.

5. Will the estimate change once work starts?
Minor refinements are normal, especially if the scope evolves. We’ll always discuss adjustments with you before moving forward.

6. How do you handle multi-language designs?
We factor in layout adjustments and text expansion, even if translations aren’t ready. You only need to confirm the language list.

7. What if I forget to include something in my link?
Don’t worry—we’ll point out any major gaps during review, so you can add details before finalizing the scope.