Free Tool

Before you hire anyone, ask these 13 questions.

Most first-time app founders have never hired a designer or developer before. They don't know what good looks like — so they can't spot what's bad until it's too late. This checklist fixes that.

Think about the person or company you're considering. Answer honestly. Takes about 2 minutes. No sign-up. No email.

Question 1 of 13 — The Process

Have they explained their process in clear steps?

A good process should be explainable in plain language before you start. If they can't tell you what happens first, second, and third — and what you'll have at the end of each stage — that's a problem.

Question 2 of 13 — The Process

Have they shown you real work — not just screenshots?

Screenshots don't tell you anything about process quality. You want to see the thinking behind decisions — why a button is here, why this flow works this way. That's what separates a designer from someone who makes things look nice.

Question 3 of 13 — The Process

Have they talked about what happens after design?

The handoff from design to development is where projects blow out. If nobody's mentioned how your designs become a built app — who develops it, how long it takes, what it costs — you're only seeing half the picture. A prototype is not a built app.

Question 4 of 13 — The Process

Did they ask about your users before your features?

Everyone arrives with a feature list. The real work is understanding who the users are and what problem you're solving. If someone jumps straight to "what features do you want?" without asking about the people who'll use it, they're building backwards.

Question 5 of 13 — Pricing & Scope

Have they given you a fixed price?

Hourly billing creates bad incentives — the longer the project takes, the more they earn. Fixed pricing puts you and your designer on the same team. Both sides want it done well and on time.

Question 6 of 13 — Pricing & Scope

Have they explained exactly what's included?

You should know the number of screens, rounds of revisions, what format the deliverables come in, and what's not included. If someone can't tell you exactly what you're getting for your money, you'll end up with surprise costs or missing deliverables.

Question 7 of 13 — Pricing & Scope

Have they talked about what's NOT in version one?

Every app founder comes in wanting more than a first version can hold. A good designer or developer has the MVP conversation early. If they agree to everything you ask for without pushback, they're either inexperienced or they're padding the scope to charge more.

Question 8 of 13 — Communication

Will you work directly with the person doing the design?

When your idea goes through an account manager, then a project manager, then a designer, things get lost. The best outcomes happen when you're talking directly to the person making the decisions about your product.

Question 9 of 13 — Communication

Have they told you how and when you'll communicate?

A good working relationship needs structure. How often do you meet? Where do you give feedback? How fast do they respond? If none of this has been discussed, you'll end up chasing people or losing momentum.

Question 10 of 13 — Communication

Did they make you feel like your idea was taken seriously?

This one's about your gut. You've been thinking about this idea for a long time. The right person will listen carefully, ask good questions, and add to your thinking. If you walked away feeling like just another project in their queue, trust that feeling.

Question 11 of 13 — Red Flags

How are they handling payment?

Milestone-based payments protect both sides. You pay as work is delivered. Full upfront payment with no deliverable checkpoints is the number one structural red flag in this industry.

Question 12 of 13 — Red Flags

What timeline are they promising?

The design phase alone takes 4 to 6 weeks for a serious project. Development takes months. If someone is promising a fully built app in a few weeks, they're either cutting corners, using templates, or they don't understand the scope. Here's what realistic timelines look like.

Question 13 of 13 — Red Flags

Have they discussed who owns the work?

Last one. When the project is done, who owns the designs? The code? The assets? If nobody's brought up intellectual property or IP ownership, you could end up paying for work you don't legally own. A professional should raise this before you have to.

Your Results

Your answers

Want to see what a good process looks like from the inside? I'm happy to walk you through how I work, what you'd get, and whether your idea is ready.

Book a free 20 minute call