Explore an illustrative estimate before discussing a proposal. For paid work, agree the deliverables, team, timing, exclusions, and payment terms in writing.
DISCOVERY
You need evidence and a first-release boundary.
Problem brief, evidence log, prioritized scope.
PROTOTYPE
You need to test how a workflow feels.
Browser prototype and a test plan.
MVP
You have a reviewed first-release scope.
Agreed workflows, quality checks, and handover.
GROWTH
You need to improve an existing product.
Prioritized changes and documented outcomes.
The planner lets you change the hourly rate, scope, and team size to compare scenarios. Your Runwise proposal sets the actual price and delivery terms after the work is reviewed.
Planning examples at $85 USD/hour and eight hours per person-day. These are calculated scenarios, not published package prices.
Includes the default 30% design, coordination, and QA allowance, rounded up. Scope and rate change the result. Operating costs and external services are separate.
Change these assumptions in the planner →Know which workflows are included, how they will be checked, and who reviews each milestone.
Budget for hosting, AI usage, third-party licenses, migration, and support alongside the build.
Agree the payment schedule, source ownership, licensing, confidentiality, and process for scope changes.
Define the security, backup, monitoring, support, and recovery work needed for your release.
Bring the core workflow, budget assumptions, and open questions together in a brief. Use it to discuss the work and the commercial commitment.
Want to talk it through first? Contact our manager on Telegram ↗