We already paid for a bespoke system. Is that money wasted?

Not necessarily. If it fits and somebody maintains it, keep it. The question to answer honestly is what happens at the next statutory change and who does the work, because that is the recurring cost a build price never included.

Can you build the one thing we need on top?

Configuration yes: documents, fee heads, price lists, grading schemes and statutory rates. A fundamentally different core process, no. We would rather decline than deliver a fit that does not hold.

How do we get our data out of a bespoke system?

It depends how it was built, which is why it is worth asking before you commission one. If it holds a database you can query, an export is straightforward and the import here is the easy half.

Compared with Custom-built software

Q: Can MjFour be customised at all?

Yes, within limits worth understanding: documents, fee heads, price lists, grading schemes and statutory rates are configuration. A fundamentally different process is not, and we will say so rather than promise a fit that will not hold.

Q: We already have a bespoke system. Can we move?

Usually. Items, customers, employees, students and opening balances import from exports or spreadsheets. The work is agreeing the correct opening position, the import itself is rarely the obstacle.

Commissioning your own software is the only way to get an exact fit, and for a genuinely unusual process it can be the right call. The comparison worth making is not about the first version, it is about who maintains it in year three, when the tax slabs have changed twice.

Side by side

What matters	With MjFour	Custom-built software
Fit on day one	Configured to how you work, within a shape we did not design around you.	Exactly what you asked for.
When the FBR slabs change	Dated statutory rules updated as part of the product, for every customer at once.	A change request, quoted and scheduled.
When the developer moves on	Support Monday to Saturday, 9am–6pm PKT, by phone, WhatsApp and email.	The person who understood the code is the continuity plan.
Adding a second branch or campus	Confirmed transfers, per-establishment statute, campus transfers that keep history.	Typically a rewrite of assumptions made when there was one location.
Cost shape	A subscription in rupees; improvements arrive without a quote.	A build cost, then a maintenance retainer, then a change request per statute update.
Being audited on the numbers	Overrides, adjustments and concessions attributable to a named user by default.	An audit trail exists if it was specified and paid for.

When Custom-built software is the better choice

If your core process is genuinely unusual, a manufacturing flow, a licensing regime, a trade with its own rules, a bespoke build will fit where a product cannot, and you should commission one. Ask the harder question first, though: who maintains it, and what happens the month statute changes and that person is unavailable.

See all products

In practice

What switching actually involves.

The comparison that matters is not version one

A commissioned build fits exactly, because it was specified by you. On the day it is delivered it is better suited to your business than any product can be. That is real and worth acknowledging.

The comparison worth making is year three.

Three questions to ask before commissioning

Who maintains it when statute changes? The salary slabs move in the budget, an EOBI ceiling is revised, a provincial rate changes. In a product these arrive as updates. In a bespoke build each is a change request that has to be specified, quoted, scheduled and tested, and it happens every year.

What happens when the developer is unavailable? For most bespoke systems in this market, continuity is one person who understands the code. That is not a criticism of them; it is a single point of failure that no contract removes.

Was an audit trail specified? Attribution of discount overrides, salary adjustments and fee concessions is the sort of requirement nobody asks for at the start, because it has no visible feature. It gets added after the first time somebody needs it and cannot have it.

What a product gives up

Exactness. MjFour is configured to how you work within a shape we did not design around you. Documents, fee heads, price lists, grading schemes and statutory rates are configuration. A fundamentally different core process is not, and we will say so rather than promise a fit that will not hold.

When to commission anyway

A genuinely unusual core process: a manufacturing flow, a licensing regime, a trade with its own rules. Then a bespoke build is the right answer and a product will fight you. Ask the maintenance questions above first, and price them in.

Moving from a bespoke system

Usually straightforward. Items, customers, employees, students and opening balances import from exports or spreadsheets. The work is agreeing the correct opening position, not the import.

Terms

Terms used on this page

Plain definitions of the words a buyer here actually searches for.

Change request: Work specified, quoted and scheduled to alter a bespoke system, which is how every statutory update reaches software nobody maintains as a product.
Key person risk: Dependence on one individual who understands a system, which no contract removes and which surfaces at the least convenient moment.
Maintenance retainer: The ongoing fee for keeping a commissioned system working, separate from its build cost and frequently omitted from the original comparison.
Configuration versus customisation: Changing settings the product already supports, against altering how it fundamentally works; the first is safe and included, the second is not offered.

Questions people ask before they buy

Twenty minutes, your own data, no slides.

Bring a month of your own sales, a payslip you argue about, or last term’s fee sheet. We will show you what it looks like in MjFour.

Request a demo Talk to us