The four options, defined
SaaS: ready-made software
A SaaS (software as a service) product is an application you rent by the month and use as it is. For invoicing and e-Factura in Romania, products such as SmartBill or Oblio handle issuing, sending to ANAF's system and archiving without any project. You pay a subscription, start the same day, and the vendor updates the product when the law changes. The limit: you work the way the product was designed, not the way your company works.
Freelancer: one specialist
A freelancer is a specialist who works alone: a developer, a designer, a consultant for a specific product. A freelancer is quick to start and usually cheaper per hour, and fits a clear task that needs one skill: a report, a small integration, a brochure website. The risk is continuity. When the freelancer takes another project, falls ill or stops, everything they know about your system leaves with them.
Large agency or systems integrator: many people, large programmes
A large agency or systems integrator has whole teams: project managers, analysts, developers, testers. It is built for large programmes with many stakeholders, group-wide ERP rollouts and formal service contracts. For a 50-person company it often means a long tender, a high minimum budget, and a senior person at the sales stage who is not seen again after signing.
Senior studio: the same people diagnose and build
A senior studio is a small team of experienced people who analyse how the company works, design the change and build it to production, with the same people from start to finish. It covers more than a freelancer (process, design, engineering, AI) and less than a large integrator. Murarum is a studio of this kind.
Comparison table
| Criterion | SaaS | Freelancer | Agency or integrator | Senior studio |
|---|---|---|---|---|
| How you pay | Monthly subscription, per user or per volume | Per hour, per day or a fixed price per task | A large project plus a maintenance contract; high minimum budget | A fixed-scope diagnosis, then a written quote per stage |
| How fast you start | The same day | Within days | After weeks or months of tendering | After a first conversation and a diagnosis |
| Scope | One standard problem, the same for every customer | One skill, one clear task | Large programmes with many stakeholders | Processes, systems and AI, from diagnosis to production, for a defined change |
| Continuity risk | Low while the vendor exists; you cannot change the product | High: everything rests on one person | Low on paper; the team can change along the way | Medium: a small team, which is why documentation and handover are in scope |
| Who owns the code and accounts | The vendor owns the software; you own your data if you can export it | Depends on the contract; often the freelancer's accounts | Depends on the contract; sometimes licensed back to you | At Murarum, the code and accounts are in your name from day one |
| Fits when | The problem is standard: invoicing, payroll, e-Factura | The task is small, clear and needs one skill | The programme is very large or needs group-level contracts | The problem is operational, what to build is not yet clear, and the company has 10 to 250 people |
When a SaaS is enough
If you issue a few dozen invoices a month from one place, an invoicing product with e-Factura built in is the right choice. You do not need a project. A project starts to make sense when invoices leave from several systems, when orders arrive from the online shop and the ERP at once, or when someone copies data from one program to another every day. The invoice automation and e-Factura guide shows where that line sits.
When a freelancer fits
A freelancer fits a task with clear edges: one integration between two systems, one dashboard, a presentation website, a fix in a program you already use. Ask for the code and access in your company's name, short written documentation and a second person who could take over. If the task grows into a system the company depends on, the continuity risk grows with it. For a presentation website, see which CMS to choose to avoid agency lock-in.
When to choose a large agency or integrator
A large agency or integrator fits when the programme involves hundreds of people, several countries or a group-level ERP, and when you need a supplier with formal processes, a large bench and contracts sized to match. A smaller company can still buy from them, but should check who works on the project after signing and what the minimum budget buys.
When to choose a senior studio like Murarum
A senior studio fits when the problem is operational and not yet defined: work is slowing down as the company grows, data lives in three places, and nobody can say which change matters most. What we offer, as stated on our site:
- We start with a diagnosis: process map, baseline and changes ranked by gain, in a written plan you keep.
- You work directly with senior people: the founder leads every engagement, and senior partners from the studio's network join when the project needs them.
- You own the code and everything we build for you, from the first commit. Provider, hosting and licence accounts are opened in your name and billed to you directly.
- Any bug that shows up after launch is covered by a 12-month warranty.
- We have been shipping products since 2012.
- Price is set on scope, after the diagnosis, with a written quote before you commit. See how we price.
The work itself sits in our Digital Transformation and Process Optimization services.
When not to choose us
- Your company is under ten people with no clear growth constraint. A good freelancer serves you better.
- The problem is standard and a SaaS product solves it. We will say so in the first conversation.
- The programme needs hundreds of people and a large supplier bench. A large integrator is built for that.
- You want extra hands by the hour inside your team. We take on defined changes, not staff augmentation.
- You need someone to write a grant application. We do not consult on EU funds; see digitalization with or without EU recovery funds.
- The launch date matters more than whether the system holds. We will not rush a build for a date.
Five questions that decide the choice
- Is my problem standard, or specific to how we work?
- Do I already know exactly what to build, or does that need to be found out first?
- How many systems and how many teams does the change touch?
- Who will maintain the system in two years?
- Whose name are the code, the data and the accounts in?
For the checks to run on any partner before signing, see how to choose a digital transformation partner.
Summary
- SaaS: right for standard problems; you adapt to the product.
- Freelancer: right for small tasks that need one skill; continuity is the risk.
- Large agency or integrator: right for very large programmes; check who does the work after signing.
- Senior studio: right for operational problems in companies of 10 to 250 people, where the same people diagnose, build and hand over.
- Whatever you choose, keep the code, the data and the accounts in your company's name.
