What makes a system cost more or less

Two quotes for “a client portal” can differ several times over, because each one assumes a different system. The price follows a handful of decisions. Once you know them, you can compare quotes fairly and choose where to spend.

• The number of user roles, and what each one may see and do.
• Connections to other systems: accounting, payments, a CRM, government platforms. Each one adds work to build and to keep running.
• Data that has to move over from old systems, and how clean it is.
• Rules with many exceptions, such as approvals, pricing or eligibility.
• Two languages, including right-to-left layouts and translated notifications.
• Mobile apps in the app stores, on top of a web version.

• A clean, simple design built from proven components.
• Standard sign-in, email notifications and file uploads.
• Reports built from data the system already holds.

Hosting, third-party services such as payments, messaging or AI usage, and maintenance all continue after launch. Ask for a monthly estimate of these next to the build price, so the cheaper quote does not turn out to be the more expensive system a year later.

Pick the one process that hurts most, build it for the people who use it every day, and leave the rest for a second phase. A smaller first release reaches users sooner, and what they tell you shapes the next phase better than a long specification written in advance.

Tell us how the work runs today. We suggest a first step sized to what matters most, and explain what drives its cost.