Five ways to handle the work, and when each one is right. The right choice depends on whether the need fits software you already own, a bounded project, a permanent team, an ongoing product partnership, or should wait.
Which one is right when
Find the row that sounds like you. If two fit, choose the simpler operating model.
A standard platform already covers most of the need
Ready to compare software proposals? Use the same operational task for each option. The custom business software buying guide provides a blank brief and a synthetic comparison with an existing-product option.
If an ongoing product partner looks like the right path, check whether the working model fits.
What you are buying in each case, what it is genuinely good at, and where it breaks.
Path 01
Can the software you already own do it?
Configure software you already own
Use Salesforce, your ERP, warehouse software, BI tooling, or another existing platform before adding custom software.
Good at
The core capability already exists and is maintained by the platform vendor.
Configuration can be faster to adopt and easier for your team to support.
You avoid owning custom code where a standard workflow is enough.
Where it breaks
Your process has to fit the platform's model and extension points.
Licensing, vendor limits, and upgrades remain outside your control.
Cross-system workflows may still need custom integration and operational ownership.
Choose it when: A standard platform already covers most of the need and adapting the process is better than building a new system.
Path 02
Should you build an in-house team?
Build an internal team
Create a permanent product and engineering capability inside the business.
Good at
The product knowledge and decision-making stay inside the company.
A full team can own a broad, continuing roadmap across many priorities.
The capability compounds when the demand is durable and leadership is in place.
Where it breaks
Recruiting and forming the team takes time and remains a management responsibility.
Engineering, product, design, QA, data, and infrastructure are different capabilities.
The fixed cost remains when the backlog changes or the initial push is over.
Choose it when: Software is a permanent core capability, the workload supports a team, and you can recruit and lead it well.
Path 03
Is a fixed-price project the right fit?
Buy a fixed-scope project
An agreed scope, price, and completion point, bought from a qualified agency or systems integrator. If the outcome is one you can name and you want us to build it, that starts on the subscription instead — the first month goes to the plan for it and the first working piece.
Good at
A number you can take to a board and a date you can plan around.
The supplier carries the estimating risk.
It finishes, and then you stop paying.
Where it breaks
It only works when the scope is genuinely known up front. When it is not, the change requests are where the money goes.
Learning something halfway through is expensive, because change is priced as change.
When it ends, the people who understand the system leave.
Choose it when: You can describe the finished thing precisely enough that a fixed price is honest, and you do not expect a queue behind it.
Path 04
When does an ongoing product team make sense?
Use Leveraged Velocity as an ongoing product partner
For more than a decade, ClearSummit has built production software for major corporations and startups. AI increases the team's leverage; clients are still buying accountable product judgment and execution. The subscription is an ongoing way to buy that product-engineering capability, working one priority at a time, on a 90-day initial term.
Good at
No hiring, and no estimate to negotiate before the work starts.
Guided includes finding and shaping the work with the people who understand the business.
What you own and what stays under your control are settled in writing before you start.
The scope and fit conditions are available to review before a conversation.
Where it breaks
A standing commitment with an initial term, not a per-task purchase.
One active priority at a time. Two at once is an expansion and it costs more.
It needs someone who can decide weekly and system access we can actually ship through. Without those it stalls.
It is the wrong shape if what you want to buy is a deliverable rather than a standing team.
Choose it when: There is more work behind the first item — or one outcome you can name and want built — you can say what the problem costs, and you want the deciding handled as well as the building.
Leave it alone and revisit when something changes.
Good at
Costs nothing.
Often the correct answer when nobody has measured what the problem costs.
Buys time to find out whether the problem is stable or growing.
Where it breaks
The cost keeps running, and it stays invisible until somebody counts it.
Workarounds harden into how the business works, and they get more expensive to undo.
The decision gets made later, under more pressure, with fewer options.
Choose it when: You cannot yet put a number on what the problem costs. Measure it for a month, then decide with the number in front of you.
ClearSummit makes sense when the work keeps changing, crosses systems, or needs product and engineering judgment without building a full internal team. If the need is standard, fixed-scope, or not yet valuable, choose the simpler path.
If the subscription is the one that fits
The fit check will tell you which option it points at, or that we are the wrong answer and what to do instead.