Free during beta

"It's just a small project"

Famous last words. You quoted for a brochure site. By week two, they want a CMS, a booking system, and "something like Airbnb but for dog groomers." Projan helps you scope properly before you commit.

Scoping on a call
  • ✕Client describes the project in vibes
  • ✕You estimate based on what they said, not what they meant
  • ✕Scope creep starts on day one because nothing was written down
  • ✕You eat the cost or have an awkward conversation
  • ✕Margin disappears on "just one more thing"
With Projan
Scoping with Projan
  • ✓AI asks the questions clients forget to answer
  • ✓Scope documented before you quote a number
  • ✓Assumptions explicit so change requests are clear changes
  • ✓Tasks broken down with real effort estimates
  • ✓Your quote is based on what the project actually is
Typical scoping session: 15-20 minutes
The hidden cost

The real cost of bad scoping

It's not just the hours. It's the relationship, the margin, and the projects you can't take because you're stuck finishing this one.

A project that's 30% under-scoped costs you 30% of your margin. On a $50k project, that's $15k you're donating to the client

Your team gets frustrated building things that weren't in the plan. Morale drops. Your best people start looking elsewhere

Timeline slips mean you can't start the next project on time. One bad scope cascades across your entire quarter

What proper scoping sounds like

Run a Projan session before the proposal goes out.

app.projan.ai
LC
Client wants an e-commerce site. Shopify, custom theme, about 50 products. They mentioned wanting some kind of loyalty programme too. I'm thinking 4-6 weeks.
P
The e-commerce part is clear. But "some kind of loyalty programme" — that's anywhere from a simple points display to a full referral system with tiered rewards. Has the client described what they actually want, or is this still an idea? Because that could easily double your timeline.
LC
It's still vague. They said something like "points for purchases."
P
I'd recommend scoping the e-commerce build as the core project and the loyalty programme as a separate phase with its own quote. That way you can deliver the store on time, and the loyalty work doesn't hold everything up while they figure out what they want. Want me to break down both phases?
Your Plan Phase 1: Shopify store with custom theme (4 weeks, 12 tasks). Phase 2: Loyalty programme (scoped separately, 3 options from simple to complex). Change request boundary documented.

Why agencies use Projan

Protect your margins

Scope is documented before you commit to a price

Change requests are clearly out-of-scope, not arguments

Your estimates are based on real task breakdowns

Professional proposals

Attach a structured plan to your quote

Clients see you've thought it through

Export to Google Docs or Notion for easy sharing

Your next project deserves a proper scope

Free during beta. Early users get 50% off for life. Run a scoping session on your next client project and see the difference.

Try it on your next project
Scope a project in 15 minutes
Export to Jira, Notion & more