We send a written scope document within 2–5 business days covering: features included and excluded, tech stack, team composition, timeline, pricing model, payment schedule and what we need from you to start. Nothing is final until you review it and agree. You can push back, ask questions or request changes before we sign anything.

• Landing page: 1–2 weeks
• Corporate site (5–15 pages): 2–4 weeks
• WordPress/WooCommerce store: 3–8 weeks
• Custom web app (mid-size): 6–12 weeks
• Large product build: 3–6 months

These are working timelines, not minimums designed to look good. We give a realistic estimate after scoping — not before.

Yes. Development runs in 1–2 week sprints. At the end of each sprint you get a demo of working features deployed to a staging environment — not a status update or a progress bar. If something is running slower than planned, you hear about it at the sprint close, not in the last week before deadline.

We log the change, estimate the impact on scope, timeline and cost, and agree before doing anything. Nothing gets added silently. Nothing gets delayed without explanation. Change is normal in development — the problem is when teams absorb changes without flagging cost and then hit you with a bill or a missed deadline at the end.

Working deployment on your production server, full source code, admin access to all systems, documentation covering architecture and key processes, and a handover call if your team is taking it over. You own everything — no leverage held on hosting, code or credentials.

Frontend: React, Vue.js, HTML/CSS/JavaScript, Tailwind. Backend: PHP, Laravel, Node.js, Python. CMS: WordPress, Headless WordPress, Strapi. E-commerce: WooCommerce, Shopify. Databases: MySQL, PostgreSQL. Infrastructure: AWS, DigitalOcean, Cloudflare. We recommend the stack that fits the project — not the one we have the most experience billing for.

Both. WordPress is appropriate for many business sites, blogs, WooCommerce stores and even lighter web apps. Custom applications (React + Node.js, Laravel, or similar stacks) are better when you need complex logic, custom data models, high performance or a product that will evolve rapidly. We tell you honestly which fits your case.

We do both, but development is the core service. For projects that need full UI/UX design from scratch we involve a designer as part of the team. If you already have designs (Figma, XD or similar) we build from those. If you have a design you are not sure about, we give you honest feedback before building.

Yes. API integrations and system connections are a significant part of our work. CRM setups (HubSpot, Salesforce, Pipedrive, custom), payment gateways, booking systems, accounting software, email marketing platforms, analytics tools — if it has an API, we can connect it. If it does not, we discuss alternatives.

You get a dedicated developer or small team that integrates into your workflow — your project management tool, your repo, your communication channel. Onboarding takes 3–5 days. Work runs in agreed cycles (sprints or monthly scope). You get the same developer consistently, not a rotating team. Rates are $29–45/hr depending on seniority and engagement length.

Staff augmentation: one or two developers join your existing team and work under your direction. You manage the work, we provide the resource. Dedicated team: a self-contained team (dev + optional designer/PM) that owns a product or workstream, reports to you, and manages their own sprint delivery. Both models are available.

Typically within 5–7 business days after contract signing. The first few days are onboarding: codebase review, access setup, aligning on the first sprint scope. Some clients go from first call to first commit in under 10 days.

We prefer a minimum of 1 month to make onboarding worthwhile for both sides. Most outsourcing clients stay for 3–12 months. There is no forced lock-in — if you need to pause or end the engagement, we agree a wind-down period (typically 2 weeks notice) so you are not left without coverage.

Yes. A significant part of our work is with digital agencies that bring us in as their development arm for client projects. We operate under NDA, never contact your clients directly and treat your relationship with your client as yours to protect. White-label arrangements are standard and no special setup is required.

Both, depending on what the project needs. Custom themes are better for performance, long-term maintainability and control. Page builders (Elementor, Bricks, Oxygen) are appropriate for sites where the client team needs to edit layouts independently after launch. We recommend the approach that makes sense for your use case and tell you the tradeoffs of each.

Yes. We handle migrations from Squarespace, Wix, Webflow, Joomla, Drupal, Magento, Shopify and custom-built platforms. Every migration starts with an audit of the existing site to understand what data, URLs, redirects and integrations need to be preserved. No migration gets started without that first.

Performance is built into the build standard, not added at the end. This includes image optimization, lazy loading, caching setup (server-level and plugin), CDN integration, script loading logic, database query optimization and hosting configuration. We target a LCP under 2.5s and CLS under 0.1 on production — not just on Lighthouse in a test environment.

Yes. Custom checkout flows, tiered pricing, wholesale B2B portals, membership-gated products, subscription logic, multi-currency, regional tax handling, custom payment gateway integrations — these are all common WooCommerce projects we handle. We assess the scope on the first call and recommend whether WooCommerce is the right tool or if Shopify or a custom solution would serve better.

Slack, Teams or Telegram — whichever you already use. Daily async updates when the sprint is active. Sprint demo every 1–2 weeks. One dedicated channel where questions get answered same day during business hours. You talk directly to the developer or small team, not through an account manager layer. If something comes up that needs a call, we schedule one — but most things resolve faster in writing.

Within a few hours during the business day for active projects. We are based in Spain (CET/CEST) and have experience working with US East Coast, US West Coast, UK, Germany, Netherlands and Australian clients. If your timezone requires early morning or late afternoon overlap, we set a fixed window that works for both sides.

Directly. There is no translation layer between you and the people writing the code. Technical questions get answered by the developer who made the decision. Scope questions go to the same person. This changes the speed of feedback loops and the quality of the answers you get significantly.

Three things you can verify independently: (1) Upwork history going back to 2006 — 500+ completed contracts, $2M+ earned, visible at upwork.com/agencies/valant. (2) Clutch reviews — third-party verified client interviews at clutch.co/profile/valant. (3) 19 years in business under the same name, no rebrand, no pivot. A track record that long is not possible to manufacture.

Upwork — 500+ completed projects, reviews locked when contract closes (cannot be edited by either party).

Clutch — verified B2B reviews involving a Clutch-conducted client interview.

LinkedIn — client recommendations on the founder’s profile.

Yes — the majority of Upwork billing comes from returning clients. Some clients have been working with us for 5+ years across multiple projects. Repeat rate is the most honest signal of whether a development partner delivers what it promises. We do not manufacture it — it is visible in the Upwork contract history.

Valant Software is based in El Campello, Valencia, Spain — an EU member state. This means standard EU contractual frameworks apply, GDPR compliance is built into how we handle data, and there are no unusual jurisdiction risks for European clients. NDAs are available before the first call if needed.

You do. Full IP transfer to the client is standard on every project. All source code, assets, design files and credentials are handed over at delivery. We do not retain any rights to the work, do not hold anything back for leverage and do not lock you into proprietary systems you cannot access or move.

You hear about it at the sprint close — not in the last week. If a sprint falls behind, we flag it, explain why, show you the options (reduce scope, extend timeline, add resource) and agree before moving forward. We do not absorb delays silently and then present a missed deadline as a surprise.

Bugs that fall within the agreed scope and acceptance criteria are fixed at no charge within a standard warranty period (typically 30 days post-launch). Bugs that result from changes made after delivery, third-party updates or new feature requests are scoped and billed separately. The distinction is clearly defined in the contract before work starts.

Yes. This is one of the more common projects we take on. We start with a code audit (2–4 days, fixed price). We document what exists, identify the real problems honestly, and give you options: continue building on the existing codebase, do a partial rewrite, or start clean. Some codebases are salvageable. Some are not. We tell you which — before you commit to anything.

Sprint demos every 1–2 weeks exist specifically to catch this before it becomes expensive to fix. If something is going in the wrong direction, raising it at a sprint demo costs one week of work to correct, not the entire project. If there is a fundamental disagreement we cannot resolve, we wind down cleanly — full handover of everything built, documentation included, no leverage held.