Quick start checklist
Quick start
- Define outcome + success metric (what does “done” look like?).
- List deliverables + file formats (e.g. Figma, PDF, source files).
- Set deadline ranges (ideal + latest acceptable).
- Share constraints (brand rules, tech stack, tone, must-avoid).
- Decide budget model: fixed scope or hourly with a cap.
- Ask for 2–3 relevant samples + a short plan + questions.
- Pick one decision‑maker + one feedback channel.
Start with a crisp brief
Define the outcome, deadlines, assets you will provide, and how you’ll measure success. Vague scopes lead to rework and stalled projects.
Share examples or references when they help—but stay flexible on execution so freelancers can propose the best approach.
Add acceptance criteria (what must be true for you to approve). For example: “Landing page loads in under 2 seconds on mobile,” or “Logo exports include SVG + PNG in light/dark.”
Evaluate proposals, not pitches
Look for freelancers who reference your requirements, propose a realistic timeline, and ask thoughtful questions.
Balance price with fit: newer talent can be excellent value if the scope matches their proven work samples.
A good proposal includes: a step-by-step plan, assumptions, dependencies (what they need from you), and how they’ll handle feedback and revisions.
Scope, milestones, and payments
Break the work into milestones tied to deliverables (not time). Each milestone should produce something reviewable: a draft, a build, a set of assets, a report.
When you’re unsure, start with a paid discovery milestone (research + plan). It’s the simplest way to reduce risk on a first hire.
Keep a final milestone for handoff: source files, documentation, access transfer, and a short walkthrough.
A simple weekly workflow
Set a predictable cadence: one kickoff call, one mid-week update, one end-week review. Freelancers move fastest when feedback windows are clear.
Collect feedback internally and send one merged message. Multiple stakeholders giving separate instructions is the #1 cause of rework.
If scope changes, decide explicitly: update timeline, budget, or deliverables — don’t silently expand the work.
Run the engagement like a lightweight project
Agree on milestones, communication cadence, and a single decision-maker on your side.
Use the platform for files, approvals, and payments so expectations stay documented if anything changes.
End each milestone with: what shipped, what changed, what’s next, and what you need from each other to keep momentum.
Common pitfalls (and fixes)
Vague scope
Add acceptance criteria, examples, and what you’ll provide. If you can’t describe “done,” you can’t manage it.
Too many stakeholders
Nominate one approver. Collect feedback internally, then send one merged message to the freelancer.
Choosing purely by price
Use price as a filter, not the decision. Fit and communication predict success more than $/hr.
Endless revisions
Limit revision rounds, schedule feedback windows, and require you to provide assets on time.
Copy/paste templates
Job post / brief template
## Goal What we’re trying to achieve (1–2 sentences). ## Audience Who this is for and what they care about. ## Deliverables - Deliverable 1 (format) - Deliverable 2 (format) ## Constraints Brand/tech/tone, must-haves, must-avoid. ## Timeline Ideal deadline: Latest deadline: ## What we’ll provide Logos/assets/access/links. ## How we’ll measure success Clear acceptance criteria. ## Please include in your proposal Relevant samples + your plan + questions + estimated timeline.
Proposal evaluation message
Thanks for the proposal — quick questions: 1) Which 2–3 examples in your portfolio are most similar and why? 2) What’s your step-by-step plan and timeline? 3) What do you need from us (assets, access, answers) to start? 4) What are the top risks you see and how would you mitigate them?
FAQ
Fixed price or hourly?
If the scope is clear, fixed price works best. If you’re exploring, use hourly with a cap or do a paid discovery milestone first.
How do I avoid getting low-quality work?
Ask for relevant samples, a realistic plan, and clarifying questions. Strong freelancers ask great questions before starting.
How should I structure payments?
Use milestones tied to deliverables. Pay for progress, not promises. Keep a final milestone for handoff/source files.
