Use Case Program
A month of Willo engineering, at no cost, to solve one specific process in your company and hand it over working.
The honest way to show what we do is not a presentation — it is building. So each year we select a limited number of companies and give them a month of engineering free of charge, with a use case running on a real process from their operation. In exchange, the company lets us document the result as a verifiable case study in our portfolio. It is an exchange of value, not a favour.
2°
year in operation, with clients in Colombia and the United States
7
companies served across fintech, retail, BPO, digital health and accounting
3
in-house technologies: our internal ERP, ByteArena and Willo Campus
What it is
- Real engineering hours, delivered by the same team that serves our paying clients.
- A formal discovery of one specific process in your company, documented and structured.
- A working solution delivered at the end of the month, in a test environment, with its technical documentation.
- Joint work: weekly sprints, with your team inside the process.
What it is not
- Not a full production rollout of the process across the organization.
- Not consulting and not an assessment: at the end of the month there is software, not a report.
- Not a throwaway demo: what we deliver is your company’s own code, and it comes documented.
- Not open-ended support or maintenance once the program closes.
What each side brings
- 180 engineering hours from a senior team, over one calendar month.
- A Tech Lead and a Developer assigned to you, with nobody in between.
- Process discovery and the technical structuring of the use case.
- A working delivery of the use case plus its technical documentation.
- Two weeks of warranty on what we deliver.
- Permission to document the use case and publish it in Willo’s portfolio.
- Use of the company name and logo as a client Willo has worked with.
- A testimonial from the executive in charge, written or on video, at the end of the month.
- A designated contact who knows the process and is available weekly.
- The access and inputs needed to execute, handed over in Week 1.
What you are getting is worth
$5.400.000 COP
Commercial value of what Willo puts in during the program month.
$0
What Willo invoices for this month. The value is given as a program benefit.
Tech Lead · 40 hours
Architecture, code review, quality control and technical direction of the case.
Developer · 120 hours
Building the use case, testing and technical documentation.
Discovery · 20 hours
Process sessions, structuring the scope and defining the deliverable.
Reference rate: COP 30,000 per engineering hour, the same one Willo applies to its commercial contracts. This value is not invoiced, is not credited against a future project, and creates no obligation to buy.
What the company has to meet
All six requirements are mandatory. Selection is made among companies that meet every one of them.
An established, operating company
With an active operation and real invoicing. Not for business ideas without activity.
One concrete, bounded process
An identifiable process with a start and an end, solvable in a month. Not a full transformation.
A committed decision maker
The manager or executive who owns the process, available for the weekly ceremonies.
Authority to grant access
Able to authorize the technical access and the process information in Week 1.
Not enough technical capacity
Companies without an internal technical team, or who need capacity beyond it.
Permission to document
Written approval to publish the use case. It is what the company gives in return.
Four phases in one month
Process discovery
Sessions with the people who run the process today. We document the flow as it is, its rules and where it breaks.
Closes with a scope document signed by both sides.
Defining the use case
From the whole process we pick the stretch that creates the most value and can be built within the month, and write its PRD.
Whatever falls outside is recorded as future scope.
Building together
Weekly sprints with planning and demo. Your contact validates every increment, and decisions get made in the session.
Nothing is built without the process being validated first.
Delivery and documentation
Final demo to leadership, handover of the code and the technical documentation.
The use case is documented and the testimonial recorded.
One month, week by week
Week 0
Approval, signing the agreement, and the checklist of access and inputs.
Week 1
Process discovery, definition of the use case, and a signed PRD.
Weeks 2–3
Building, in weekly sprints. Progress demo every Friday.
Week 4
Testing with the people who run the process, adjustments, and working delivery.
Close
Leadership demo, case documentation, testimonial, and two weeks of warranty.
Kick-off checklist
Delivered in Week 0. The schedule starts once it is complete.
A designated contact
Name, role and contact channel of whoever answers for the process.
Process documentation
Whatever manuals, forms, templates or records exist today, in whatever state they are in.
Technical access
Credentials or service accounts for the systems involved: ERP, CRM, email, APIs.
Test data
A representative sample, anonymized if it holds anything sensitive.
Time on the calendar
The three discovery sessions and the weekly ceremonies, already scheduled.
Documentation approval
Written approval to publish the use case, with whatever scope is agreed.
What gets published
- The company name and logo as a Willo client.
- The business problem addressed, described in general terms.
- The solution built and the technologies used.
- Screenshots or video of the solution, using demo data.
- A testimonial from the executive in charge, written or on video.
What does not
- Financial figures, margins or business volumes.
- Data about clients, suppliers or employees.
- Source code, credentials or internal architecture.
- Operational detail that amounts to competitive advantage.
- Anything the company marks as confidential during review.
The rules of the program
The month does not extend
The program runs one calendar month. It is not extended, and unused hours do not carry over.
One use case
One process, one scope set in the PRD. Changes of scope are recorded as future work; they do not replace what was agreed.
Delivered to a test environment
Production rollout and integration across the operation belong to a separate project.
Two weeks of warranty
Fixing defects in what was delivered. It does not cover new features. Once it ends, there is no support without a contract.
Infrastructure and usage
Hosting, licences, databases and AI model usage are on the company.
Ownership of the deliverable
The use case code belongs to the company. Willo keeps its own pre-existing internal tools and components.
Confidentiality
Willo signs an NDA. Nothing sensitive is published without explicit approval.
Early termination
If the company does not provide inputs or misses the ceremonies for two consecutive weeks, the slot goes to another company.
When the month ends there is no obligation to hire. If the company decides to continue, it does so with a working use case, a scope already validated and a team that knows its process. If it decides not to, it keeps the deliverable and the documented process.
Three ways to keep going with Willo
Support & Upkeep
Monthly hours
- Maintenance of the use case delivered
- Fixes and minor adjustments
- One person assigned to support
For those who want stability without widening the scope.
Dedicated Team
Extended monthly hours
- Willo as a multiplier for your technology area
- Tech Lead and Developer assigned
- Weekly sprints, planning and demo
- Scope that flexes month to month
- No hiring or payroll costs
The model we run with our recurring clients.
Fixed Project
Fixed scope and deadline
- Full production implementation
- Price and schedule agreed up front
- Quoted against the use case PRD
- 6 weeks of functional warranty
For those who already know exactly what to build.
The final quote is issued against the use case PRD, with scope and schedule agreed. Book a call to find out the investment.
What people usually ask us
Let’s start with your process
Tell us which process is eating your hours today — book the requirements validation session.
Confirm your interest
You reply to this proposal and tell us which process is the candidate.
We check the requirements
A 45-minute session to go through the six requirements and whether a slot is open.
The month starts
Signing the agreement, the access checklist, and the first discovery session.