Quick start
This walkthrough takes you from a new account to a versioned, estimated scope.
1. Create your account
Sign up at app.scopingly.io with your work email. After verifying your email you land in a 14-day Pro trial — full access to Pro features, no card required. When the trial ends you drop to the Free plan (1 seat, 3 documents) unless you upgrade.
Signing up also creates your organization. You are its owner. Everyone you invite joins the same organization and shares its documents, teams, and plan.
2. Write a PRD
A PRD (product requirements document) is where a piece of work starts. Create one from the Requirements page and write it like you normally would — problem, goals, requirements, out-of-scope, non-functionals.
As you write, Scopingly can detect gaps: a missing success metric, an unspecified non-functional, a dangling integration reference. Gaps are advice, never a gate — you can resolve them, ignore them, or approve the PRD anyway. See PRDs.
3. Invite reviewers (optional)
Attach reviewers to a PRD and move it through its approval lifecycle: request review → reviewers sign off → the owner approves. Approval is versioned, so the approved artifact is immutable and auditable.
4. Generate a scope
From an approved (or draft) PRD, generate a scope document. Scopingly produces a structured breakdown — deliverables, effort, assumptions — and stamps it with provenance: the exact PRD version it came from. If that PRD version is later superseded, derived scopes are flagged as drifted. See scope generation.
AI generations are metered
Scope generation, executive summaries, and epic generation consume your plan's monthly AI generation allowance (Free 10/mo, Pro 50/seat, Business 150/seat, Enterprise unlimited). Deterministic gap detection does not. See billing & quotas.
5. Commit a version
When the scope is right, approve it. From that point it is immutable — to change it you fork a new version that supersedes the old one, leaving a signed changelog of what changed and why. This is what gives calibration a real baseline to measure against. See scope versioning.
6. Project a date and feed back actuals
Set a target date and the compression meter tells you whether the team's own estimate fits — and if not, which deliverables would have to give. As real effort lands, feed actuals back in and Scopingly calibrates future estimates to your team's real-world bias.
Where to go next
| You want to… | Read |
|---|---|
| Understand the vocabulary | Core concepts |
| Manage who can do what | Roles & permissions |
| Connect JIRA or Slack | Integrations |
| Compare plans | Pricing |
| Integrate over the API | API overview |