Based in Groningen · Working internationally

Tinsights, websites, software en apps
Discuss a project

Web applications

Web applications built around the daily work.

A marketing website informs. A web application is where people sign in and do the work.

Portals, dashboards, planning, bookings and customer environments. Tinsights builds web applications with accounts, permissions and data. It is not an extra page on the business website.

If visitors mainly need to read and get in touch, a website is enough. If they need to sign in, see status or keep data, it belongs here.

Website or web application

Website

Explain services, be found, send an enquiry. Public, mostly reading.

Web application

Sign in, roles, manage data, repeated tasks. Private or partly private, mostly working.

What we build

Environments that hold the process.

  • PortalsCustomers or partners who see their own work, files or status.
  • DashboardsFigures and queues someone actually uses, not a screenshot chart.
  • SaaSA product with accounts, subscription logic and room to grow.
  • Planning and bookingsWho reserves what when, with the rules you now keep in your head.
  • Internal systemsThe team’s work, without yet another loose tool.
  • Permissions and dataRole-based access and management of the records that matter.

Use cases

Where a web app makes the difference.

  • Customer environment

    Follow jobs, fetch documents, no mailbox as archive.

  • Internal operations

    Receive, assign and finish requests.

  • Reporting

    The same source for everyone, instead of five spreadsheets.

How we work

Screens follow the work.

  1. Collect the tasks

    What someone must be able to do in the system on a weekday.

  2. Model and permissions

    Which data exists, who may see it, what a mistake costs.

  3. Build in steps

    The core flow first, then reporting or extra roles.

  4. Care

    Hosting, updates and further development on the same codebase.

Engineering

The parts under the screens.

  • AccountsSign-in, sessions, passwords or SSO when needed.
  • RolesNot everyone sees the same. That lives in the application, not in agreements.
  • DataClear tables and validation, not a dump.
  • APIsOther systems can use the same source.

Questions

Is a web application the same as a website?

No. A website is mostly public and informative. A web application has accounts, data and repeated use. Sometimes a business needs both.

Can customers and staff use the same app?

Yes, with different roles. Or as two environments on the same backend. We decide from the process.

Does Tinsights also host the application?

Yes, that is possible. Deployment, backups and monitoring belong with technical management after launch.

Do you need more than a website?

Describe who must sign in and what that person must be able to do. Then it is quickly clear if this is the right route.