What you can count on when working with Valant Software
Guarantees in development are only worth something if they are specific, honest and actually followed through. This page explains exactly how we protect clients on every project — through written scope, sprint visibility, clean code handover, IP ownership and continued access after delivery.
What a guarantee from a development agency actually means
Most “guarantee” pages in this industry are marketing language. Broad promises like “we guarantee your satisfaction” or “100% quality guaranteed” are not actionable and create no real protection. What actually protects a client is a clear written scope before work starts, regular visibility into progress during the project, unambiguous IP transfer on delivery and honest communication when something is off track.
That is what this page covers. Not slogans — specific commitments about how we run projects, what you receive, and what we do when things do not go as planned. All commitments here apply to projects with a signed statement of work or active contract. They do not apply to informal conversations, unsolicited requests or work performed outside a documented agreement.
What we commit to on every project
Seven specific practices that protect clients from the most common ways development partnerships go wrong.
Nothing gets built before you have a written document defining what is in scope, what is explicitly out of scope, the tech stack, the team composition, the timeline and the pricing model. This is not an estimate subject to revision after payment — it is the agreed baseline for the engagement.
We do not disappear for six weeks and deliver a finished product. Development runs in 1-to-2 week sprints. At the close of each sprint you see a working demo in staging — actual features, not a slide deck. Problems and delays are flagged at the sprint close, not at the final delivery date when it is too late to make decisions.
When requirements change — from either side — we log the change, estimate the impact on scope and timeline, and agree in writing before any work related to that change begins. Changes are never added to the build silently and never billed at the end without prior agreement. This applies to feature additions, scope reductions and technical pivots.
On completion of a fully paid project, all code, design assets, documentation and credentials belong to you. We do not retain ownership, access or licensing rights. The repository is yours, the admin credentials are yours, the deployment is yours. We hold nothing as leverage after handover.
Bugs that are directly attributable to our implementation and surface within the agreed post-delivery support window are resolved at no additional charge. This applies to issues in the code as delivered. It does not apply to issues caused by third-party platform updates, client-side modifications made after handover, or new requirements added after project close.
We sign NDAs before any substantive business information is shared — no request needed, no delay. All project data, technical specifications, business logic, access credentials and any information shared by the client in the course of the engagement is treated as confidential and is not disclosed to any third party.
You communicate with the people writing your code. Questions about technical decisions are answered by the developer who made them. There is no account manager translating between you and the team, no 48-hour email response window, no ticket system that turns a 5-minute conversation into a 3-day wait. This is how we have run every project since 2006 and it is not something we plan to change.
How our approach compares to what most agencies do
Not a claim to be better than everyone. A plain comparison of specific practices.
| Practice | Common agency approach | How Valant handles it |
|---|---|---|
| Scope document | Broad estimate, refined “after kickoff” — often means after you have paid a deposit | Written scope with feature list, exclusions and pricing before any payment |
| Progress reporting | Status updates on request, finished product shown at the end | Sprint demos every 1–2 weeks — working features in staging, not slides |
| Scope changes | Added silently during development, billed as a surprise at final invoice | Logged, estimated and agreed in writing before any related work begins |
| Code ownership | Sometimes retained until final payment; occasionally unclear in contracts | 100% transferred to client on delivery after full payment — unambiguous |
| Post-delivery contact | Response times drop significantly after project close | We stay reachable; post-launch issues handled through the same channel |
| Communication layer | Account manager relays messages; technical questions take days to answer | Direct developer access from day one; questions answered same day |
| NDA | Available but often requires a separate legal review process | Signed before the first substantive conversation on request, no delay |
Why these practices make Valant a reliable long-term partner
The things that make a development partner trustworthy for repeat and long-term work are not marketing promises — they are consistent practices visible in a track record.
19-year operating history
Valant Software has been operating since 2006 under the same name. The track record is long enough to verify independently through Upwork contract history, Clutch interviews and LinkedIn. A company that has not had to rebrand or restart after 19 years is a company that has handled disputes and difficult projects without burning client relationships.
Verifiable reviews, not just claims
500+ completed Upwork projects with locked reviews — the platform does not allow post-submission editing by either party. Clutch reviews involve a third-party client interview. The aggregate rating across platforms is 4.9/5. These are independently verifiable, not self-reported numbers.
High repeat client rate
The majority of Upwork work over 19 years comes from returning clients — clients who were not disappointed the first time. Repeat rate is a more honest signal of reliability than any written guarantee, because it reflects real behavior: clients who received what was promised kept coming back.
EU-based, GDPR-compliant operations
Valant Software is based in El Campello, Valencia, Spain. EU-based operations mean standard European contractual protections, GDPR-compliant data handling and no unusual jurisdiction risk for clients in the EU and UK. Contracts can be governed by Spanish law or another agreed jurisdiction depending on the client’s preference.
Competitive pricing with transparent structure
Rates are competitive with comparable Eastern European development agencies while operating under EU jurisdiction and legal frameworks. Fixed-price and time-and-material models are available. Pricing is discussed openly in the first conversation — there are no opaque retainer structures or hidden fees added after contract signing.
Honest advice, not just execution
We tell clients when a technical decision is likely to create problems, when a timeline is not realistic, and when a feature will cost significantly more than expected. The goal is not to win a proposal — it is to deliver something that works and keep you as a client beyond the first project. That incentive alignment produces more reliable behavior than any formal guarantee.
Questions about protection, ownership and reliability
Who owns the code after the project is finished?
The client owns 100% of the code, design assets, credentials and IP on any completed and fully paid project. Everything is transferred on delivery: repository access, admin accounts, third-party licence keys and documentation. We retain no access or ownership after handover.
What happens if something breaks after delivery?
Bugs directly attributable to our code and surfacing within the agreed post-delivery support window are resolved at no additional charge. Issues caused by third-party platform changes, client-side modifications after handover or new requirements are handled as a separate engagement. The distinction is always discussed and agreed before work starts.
Is Valant a reliable partner for long-term outsourcing?
The best answer is the track record: 19 years in business, 500+ completed Upwork projects, $2M+ earned on the platform, 4.9/5 average rating, and a high proportion of returning clients. These are independently verifiable through Upwork and Clutch — not self-reported claims.
Do you sign NDAs and confidentiality agreements?
Yes. We sign NDAs before the first substantive conversation on request — no delay or legal review process required. All project information is treated as confidential regardless of whether an NDA is in place. White-label arrangements for agencies are also standard.
How are disagreements or scope disputes handled?
Most disputes in development come from unclear scope or communication gaps, not bad faith. We prevent most of them by writing scope before work starts and logging every change. When a disagreement arises, we address it through direct conversation, documented in writing, before continuing work. The written scope document is the reference point for any dispute.
What pricing model do you use — fixed price or time and material?
Both are available. Fixed price works well when scope is stable and well-defined. Time and material works better for evolving products where requirements change as development progresses. We explain which model makes more sense for a given project during the scoping conversation, and recommend the one that protects you financially rather than the one more favorable to us.
Ready to discuss your project with a team that follows through?
The first conversation is free and there is no commitment to move forward from it. We will ask the right questions, give you an honest picture of what the project requires and send a written scope before you pay anything. If that sounds like how a development partnership should start, let us talk.