Client portal and internal system development

I build systems that staff and customers use every day: operator and expert workspaces, portals with access control, reports and data imports. I design data models and permissions before development starts so the system can grow.

Why clients come

  • The process lives in spreadsheets and chats, and the data drifts apart
  • Staff need different permissions, but right now everyone sees everything
  • Reports take hours to put together by hand
  • The system has to exchange data with a CRM, POS or HR system

What I build

  • Roles and permissions

    Employee, manager, admin, external partner — each sees their own data and actions.

  • Workspaces

    Order feeds and task queues with filters, statuses and real-time updates.

  • Imports and exports

    Excel uploads with a preview before saving, background reports with an emailed link.

  • Configurable forms

    Fields, tables and forms that admins change in settings without a developer.

  • Audit log and publishing

    Who changed what, publishing and revoking documents, protection from accidental edits.

  • Integrations

    REST APIs for partners, data exchange with CRM, POS and external services.

Relevant experience

What drives the cost

I send a stage-by-stage estimate after a call and a review of requirements.

  • Number of roles and complexity of access rules
  • Data volume and reporting requirements
  • Integrations: whether external systems have documentation and APIs
  • Hosting: cloud or company servers

FAQ

Can you integrate with our CRM or accounting system?

Yes, if the system has an API or exports. I review the documentation before estimating — the scope depends on it a lot.

Can the system run on our servers?

Yes, that's taken into account at the architecture stage. MediArchive, for example, shipped as SaaS, as a boxed product and as an on-premise install.

Do you work alone or with a team?

I own the architecture, frontend and backend myself. If the project needs a designer, QA or DevOps, we agree on the team at the start.

What do you need to estimate a project?

Tell me what problem the product solves, who will use it and which systems it connects to. If there are no requirements yet, we'll work them out on a call, then I'll send a stage-by-stage estimate.

Why is the price shown as “from”?

It's the lower bound of the budget. The final figure depends on roles, integrations and load requirements — I give an estimate after reviewing the task.