0 licences

Software that is yours — with no monthly fee per user.

Off-the-shelf products charge per user and per month, and do exactly what their vendor imagined. A custom application is an investment in code that stays yours: it adapts to your process rather than the other way round, and it does not get more expensive when you hire your fifth person.

— What it includes

Everything an internal system needs.

A web application is not a big website — it is a tool people use every day, so it is measured by how quickly work gets done in it. We work on two platforms we know well: Laravel for systems built from scratch — that is how masterbih.me was built — and Drupal when the application sits alongside content and users you already have. For MontenegroProspects we built an internal Drupal application for managing and selling property.

Users and roles

who sees what and who may change what, down to a single field

Records and workflows

statuses, tasks, deadlines, approvals — the way your process already runs

Reports and export

filters, summary views, export to Excel and PDF, printing

Integrations

REST API, accounting and ERP, payments, email and SMS

Notifications

in the app and by email, per event and per deadline

Change log

who changed what and when — essential as soon as more than one person enters data

Hosting and backup

on Anart infrastructure, daily backups, monitoring

Maintenance

security updates and support — part of the model, not an add-on

— How we work

  1. 01

    Brief and analysis

    What you do by hand today, in which spreadsheets and in which programs. Without that, software gets written for an imagined process.

    ~3–5 days
  2. 02

    Data model

    Entities, relations, access rights. The phase where mistakes cost the least.

    1–2 weeks
  3. 03

    Screen prototype

    A clickable prototype of the key screens. Your people try it before any logic is written.

    1–2 weeks
  4. 04

    Development

    Laravel or Drupal — the choice is made in the previous phase, with the reasons written down. Work proceeds in phases, each on a test environment you can open at any time.

    4–8 weeks
  5. 05

    Launch, training, maintenance

    Data migration, training for administrators and users, 90 days of support after launch.

    3–5 days
Frequently asked

What clients ask about web applications.

Laravel or Drupal — how do you choose?

By what the application does. We use Laravel when the system is built from scratch and the logic is specific to your business. Drupal when the application sits alongside content, users and roles you already have — that is how we built the internal application for managing and selling property for MontenegroProspects. We make the decision in the data model phase and explain it before work begins.

Who owns the code?

You do. The complete code is handed over at the end of the project, with instructions on how to run it. We do not keep clients tied to us by withholding their code.

Can you take over an application someone else built?

We can, but only after a code review — an estimate without one is not an estimate, it is a guess. The review is a separate, short job that ends with a written report, with no obligation to continue with us.

What if the scope changes mid-project?

Work runs in phases, and each has its own price and deadline. A change that arrives mid-phase goes into the next one, with an estimate before it is accepted — so there is no hidden work and no hidden bill.

Where is the application hosted?

On Anart infrastructure, with daily backups and monitoring — the same infrastructure our websites run on. It can also run on your own server, if company policy requires it.

Do we also need a website alongside the application?

Not necessarily. An application can be entirely internal. If it is meant for your clients too, it usually comes with a landing page — that is a separate, small job.

— You might also want

The next step

Let us talk about your project.

Start the conversation → contact@anart.studio