Keep paying for SaaS or build in-house?

Enter your company's numbers, adjust the assumptions and see the real cost of both paths side by side, year by year. No sign-up, no guesswork.

Develop with a specialized partner
Analysis horizon

Path 1

Stay on the SaaS

The cost of keeping the software you already pay for (or subscribing to a new one).

R$ /month

Licenses, seats and modules you pay for today.

%/yr

How much the contract goes up per year. Also applied to the extra costs.

R$ /year

Integrations, customizations, consulting and training tied to the SaaS.

R$

Use this if you are evaluating a new SaaS. If you already use it, leave zero.

Path 2

Build an in-house team

The cost of creating a team to build and maintain your own system.

Team
Role Salary/month Qty. Dedication

Gross monthly salary, before payroll taxes — those go in the field below. Dedication is the % of the person's time devoted to the system over the analysis horizon.

× salary

Social charges, paid leave and benefits. Common range in Brazil: 1.6× to 2.0×.

%/yr

Union adjustments and promotions.

R$ /month

Cloud, development licenses and equipment.

months

During this period, the SaaS fee is still being paid in parallel.

Team setup cost Calculated from the team: recruiting each position (salaries per hire, proportional to dedication) + months of payroll with taxes as ramp-up cost — the new team's learning curve plus the current team's time on interviews, onboarding and knowledge transfer. Both assumptions are editable below.

—

salaries/hire
months of payroll

One-time cost at the start, recalculated automatically from the team and the assumptions above.

The analysis opens on screen and you get the PDF by email.

Result

Total cost of both paths over the chosen horizon, using the assumptions you set above.

Stay on the SaaS

—

Licenses, extras and implementation over the period.

Build an in-house team

—

Difference over the horizon

—

Cumulative cost, month by month

Stay on the SaaS In-house team
Period SaaS (annual) In-house team (annual) SaaS (cumulative) In-house team (cumulative)

What makes up the SaaS cost

  • Licenses over the period —
  • Extra costs over the period —
  • Implementation (one-time) —

What makes up the in-house team cost

  • Payroll with taxes over the period —
  • Infrastructure and tooling —
  • Team setup (one-time) —
  • SaaS paid during the transition —

This is a simplified estimate to support the decision, with fully editable assumptions. It does not replace an accounting or tax analysis. Costs such as turnover, team management and project execution risk are not included and tend to increase the cost of the in-house path.

There is a third path

The first step is knowing what each path costs — that is what the numbers above show. From there the math is simple: hiring a specialized firm to build your system pays off when the investment stays below the cheaper path within the horizon.

Path 1

Stay on the SaaS

—

A recurring cost forever, and the system is never yours.

Path 2

Build an in-house team

—

Your own system, but with a permanent fixed cost and the challenge of hiring and retaining tech talent.

Path 3

Hire a specialized firm

—

This is your reference ceiling: the cheaper path above. A system delivered below this amount pays for itself within the horizon.

  • One-time investment defined in a proposal, no permanent payroll
  • A custom system that is yours at the end
  • Faster delivery than structuring a team from scratch
  • Maintenance contracted only as needed
Request a quote from Starbridge Or see how we work →