Questions before you start
The details that most often determine fit, scope, and the right next step.
How much does Feature Development cost?+
Projects start at $7,500. Scope depends on the capability, existing platform, UX, data, integrations, permissions, administration, external services, and quality requirements. The project is defined around deliverables and milestones rather than a package or open-ended developer hours.
How long does a feature project take?+
Most projects take 3–10 weeks. A contained tool or integration can be shorter; portals, advanced search, multi-role workflows, or complex data and AI features can take longer. The project scope sets the specific milestones before implementation begins.
What kinds of features can Valiance build?+
The service is for meaningful additions to an existing platform, including search and filtering, customer or member portals, accounts and saved experiences, dashboards, interactive tools, calculators, connected workflows, API integrations, matching, recommendations, and AI-assisted capabilities. The correct scope follows the business problem, not a technology list.
How do we know whether this should be a feature project or a rebuild?+
The first question is whether the existing platform remains appropriate once the feature is added. If the request exposes broader UX, architecture, design, or system problems, Website Rebuild may be the more responsible recommendation. If the platform itself must change first, Platform Migration may come before the feature.
Can you build inside our existing stack and work with our internal developers?+
Yes, when the current platform is healthy enough to support the work. Valiance can build directly, work within the existing repository and deployment process, or collaborate with internal developers through clear scope, tickets, acceptance criteria, implementation review, and QA. This is a bounded feature project, not staff augmentation.
Should we build this custom or use existing software?+
That decision is part of the early review. If an established product solves the actual workflow well, custom development may be unnecessary. Custom work is appropriate when the workflow, data, integrations, or user experience require a level of fit that existing software cannot provide cleanly.
Do we need a Feature Assessment first?+
Not always. Straightforward projects can often be scoped directly. A Feature Assessment may be appropriate when the architecture, data, integrations, requirements, or AI feasibility are unclear. It is a separate paid engagement, typically $1,000–$2,500, that defines the problem, scope, approach, major risks, and initial implementation estimate before a larger project begins.
How are Feature Development projects billed?+
Projects under $15,000 typically use a 50% payment to begin and 50% before production launch. Projects of $15,000 or more typically use a 40% payment to begin, 30% at an agreed mid-project milestone, and 30% before production launch. The exact milestones are confirmed in the project scope before work begins.
Who owns the feature after launch, and what support is included?+
The client should own the relevant feature code, repository access, platform accounts, credentials, configuration, documentation, and third-party accounts, subject to provider licensing terms. The project includes a 30-day post-launch stabilization period for defects within the delivered scope. New functionality and ongoing maintenance are separate decisions.
What will you need from our team?+
We need a decision-maker or internal feature owner, access to the existing platform and codebase where relevant, technical documentation, data and integration access, and timely input from the people who will use or administer the feature. Your team should not need to project-manage the work day to day.