CreeplessUse casesWeb and app development agencies
Stop free work at web and app development agencies.
Creepless for development
In development, half the “bugs” clients report are new features in disguise. Creepless checks every request against what the client pays for, so included work goes ahead and extra work becomes a quote they approve first.
Where the hours go
Common scope creep in development work.
Typical setup: Monthly support and maintenance plan with a bug-fix allowance and a set number of dev hours.
Integrations with new third-party tools
Performance and refactoring work outside maintenance
Urgent out-of-hours fixes
Example scope rules
Write the line down once.
| Included in the plan | Quoted as extra |
|---|---|
| Bug fixes on existing features | New features |
| Dependency and security updates | New integrations |
| Up to 8 dev hours a month | Out-of-hours emergency support |
How requests get checked
Three requests. Three calls.
“The contact form stopped sending emails.”
IncludedA bug in an existing feature is covered by the plan.
“Can users log in with Google as well?”
ExtraA new feature, so it becomes a quote.
“The dashboard feels slow lately.”
Needs reviewCould be a bug or a performance project. Investigate before deciding.
Questions
Scope creep in development, answered.
How do I tell a bug from a feature request?
A bug is an existing feature not working as specified. Anything that adds behaviour the spec never included is a feature request, and can be quoted.
What should a software maintenance plan include?
Typically bug fixes on existing features, security and dependency updates, and a capped number of hours. New features and integrations sit outside it.
Other teams using Creepless: Web design agencies, Digital marketing agencies, SEO agencies, Social media agencies, Branding and design studios, Video production agencies, Freelancers.