Task Scope · 28 examples
What counts as a task?
If it can be clearly described, scoped to under 40 hours, and shipped by one engineer in 3–5 days — it's a Boundev Task.
The rule
One developer. One deliverable. 3–5 days.
If it can be clearly described and shipped by one engineer in a business week, it's a task. If it's bigger, we break it into tasks.
Tasks we ship every day.
Each one ships in 3–5 days by a single vetted engineer.
Frontend & UI
5 examplesBackend & API
5 examplesIntegrations
5 examplesDevOps & Infrastructure
4 examplesBug Fixes & Performance
4 examplesTesting & Quality
4 examplesThese are projects, not tasks.
But we have solutions for those too.
Need more than tasks?
When you outgrow one-off tasks, we scale with you.
Still have questions?
What if my request is too big for a single task?
We break it down. During scope review, if a task exceeds the 3–5 day window, we split it into smaller, shippable pieces. Each piece is a separate task that delivers working, production-ready code.
What if I'm not sure if something is a task?
Submit it anyway. Our scope review team evaluates every submission within 48 hours. If it's a task, we start work. If it's too big, we tell you how we'd break it down. If it's not a fit, we recommend the right service. No cost to find out.
How are tasks different from projects?
A task is a discrete, scoped unit of work — one developer, one deliverable, 3–5 days. A project is a larger initiative with multiple dependencies. Boundev Tasks handles the former. For projects, we offer Staff Augmentation and Dedicated Teams.
Can I submit multiple tasks?
Yes — sequentially. Starter and Growth plans handle one task at a time. When a task is delivered, submit the next one immediately. Scale plan handles two in parallel.
Not sure if it's a task? Submit it anyway.
We'll scope it within 48 hours and tell you exactly how we'd handle it — for free.
