Web systems and SaaS, from MVP to paid product.

Internal dashboards, customer portals and products with login, plans and payments. I start with the smallest system that solves the problem and grow it from real usage.

What the project includes

Login and permissions

Accounts, access levels and passwordless login when it fits, as in DeuOk.

Plans and payments

Subscriptions, one-off charges and free trials connected to your payment provider.

Security and privacy

Protected data, terms of use, a privacy policy and only the personal data you need.

Dashboard with your numbers

The numbers you need to follow, without exporting spreadsheets every week.

Project types

Your own product (SaaS)

From idea to first paying customer. DeuOk, for artwork approvals, started that way.

Customer portal

Orders, files, invoices and history in one place, behind a login.

Internal system

To retire the shared spreadsheet nobody trusts anymore.

Approval portal

Flows where someone needs to see, comment and approve something, with a date and time record.

Discovery

I learn how the process works, where time gets lost and what is worth automating first.

Prototype

A clickable version to validate the idea before the full investment.

Build

Frequent deliveries, with access to the test environment from start to finish.

Evolve

Monitoring, adjustments and new automations as the business grows.

Frequently asked questions

What is an MVP?

The smallest version of the system that already solves the main problem. It lets you test with real users before investing in secondary features.

Can I start small and grow later?

Yes, and that is what I recommend. The foundation is planned to take new features without a rewrite.

Does it work on phones?

Yes, it is responsive. If you need an app in the stores, see Mobile apps.

Is some process slowing your team down?

Tell me how it works today and I will tell you what can be automated.