At Solarte, we've designed a process of working on software projects that supports predictable budgeting with value-based pricing, yet allowing for a flexible, iterative approach to defining the details of the solution. Let me describe how it works.
During our initial consultation, we'll ask you to provide a brief description of your company: what you do, how you operate, what your priorities are and what challenges you're looking to solve. This involves open-ended questions where we will mostly be listening.
The next step involves discussions about features: what is required, what might be useful, how it should work and so on. It continues until we have a mutual understanding of the general shape of the system. We don’t need all the details, just a list of modules and features with expected complexity. If during the development process you request a change that doesn't affect complexity, it will not change the price or timeline. If it is more complex, we will still be happy to accommodate and propose an adjusted timeline and price.
Then we will prepare an initial specification, time plan and quote - everything required for a contract. Once it is signed and initial payment is transferred, development begins.
We don’t work using scrum. We work in an agile manner but according to the principles of the original Agile Manifesto. This means that you don’t need to wait until the next sprint ends to see your request implemented - it will be done as soon as it can be safely applied. This doesn't mean that changes are implemented ad hoc - every change has to be analyzed against current requirements and architecture but still typically within days rather than weeks.
We always start with creating the architecture and user experience design. I will explain how it will benefit the project in my next videos. Using our AI-powered platform to accelerate development, we can create the first testable version very quickly which will be shared with you.
During development, we will be meeting regularly and discussing the details of the solution with you. Here we will have more detailed questions, requests for specific information, and we will guide you through the process and suggest solutions. Conclusions will be added to the specification and implemented soon after. Each time, you will receive a change log, the current version of documentation with diagrams, and you will be able to test it and comment.
When all features are implemented, you will have two weeks for testing. If for any reason you do not like the solution, you can walk away without any additional cost and the project will be deleted. If you accept it, you will receive a final invoice. After payment, it will be deployed to production and you will get the source code.
During the first year, all change requests will be priced with the same discount as at the beginning.
Any time you find a bug, you can report it to us and it will be fixed for free. With us, you always pay only for the value you are receiving.
Initial Consultation: Listening First, Then Designing
Our collaboration starts with a conversation - not a checklist.We’ll ask open-ended questions to understand:
What your company does
How your processes work
Your current priorities and challenges
This stage is focused on listening, not selling. The goal is to understand your business so the software can be built around it - not the other way around.
Defining Scope Without Getting Lost in Detail
Once we understand your business context, we move into the feature discussion phase:
What is required?What might be useful?How should it work?
What might be useful?
How should it work?
You won’t need to define every single interaction upfront. We’ll work together until there’s a shared understanding of the system’s general structure - modules, features, and estimated complexity.
Note: If later you decide to change something that doesn’t affect complexity, it won’t impact price or delivery time.
From Agreement to Action: Agile Development Without the Buzzwords
Once we agree on scope, you’ll receive a specification, timeline, and quote - everything needed to sign a contract and get started.
Why We Don’t Use Scrum (And What We Do Instead)
We follow the original Agile Manifesto - not modern Scrum ceremonies. That means:
You won’t have to wait for a “sprint review” to see updates
Improvements can be delivered in days, not weeks
Every change is assessed against architecture and requirements for safety and stability
This flexibility is made possible by our AI-powered platform, which speeds up the creation of architecture, documentation, and code - so your first testable version arrives fast.
Iteration and Feedback: Collaborative Development
Throughout development, we meet with you regularly to:
Refine details
Ask targeted questions
Present testable updates
You’ll receive:
Updated documentation and diagrams
A detailed change log
Access to the latest version for review and feedback
This means you always know where the project stands - and can influence the outcome in real time.
Final Testing and Handover: You Stay in Control
When all features are complete:
You get two weeks to test the solution
If you’re not satisfied, you can walk away at no extra cost
If accepted, you receive a final invoice, and we deploy to production
You receive the full source code
Peace of Mind: During the first year, all change requests are priced at the same discounted rate, and all bug fixes are handled for free - forever.
Built Around Value, Not Hours
At Solarte, you don’t pay for time - you pay for outcomes.By combining value-based pricing with a process that’s fast, transparent, and collaborative, we ensure your software is:
Built around how your business actually works
Ready to adapt as you grow
Delivered with predictable costs and zero surprise fees
