Contacts

Navigation

Two monitors on a dark walnut desk at night: a web application dashboard with a sidebar, data table and chart on one, a code editor on the other, and a phone in front showing the same app in a single column.
Design & development

Web applications.
Built for purpose.

Give customers and teams a better way to get things done. Vermilio combines creative thinking with web development to shape apps around your business goals.

Make the next task easier.

A web app lets people take action in their browser — a SaaS product, a client portal, a custom CRM. Start with the task they need to complete, then choose the tools that help.

01 /
A laptop displaying a ceramic lamp product page with product details and an Add to bag button.

Customer spaces

Give people a clear place to view details, send requests, or track progress. Plan what each person can see and change from the start.

02 /
Connected web application icons for task management, messaging, analytics, client access and file sharing.

Tools for your team

Bring a shared task into one place. Map how work moves between people so the app supports real habits and reduces repeat steps.

03 /
A website sitemap and planning notes beside a laptop.

Guided choices

Help buyers work through a complex choice. A guided form or product selector can turn a long list of options into a clear next step.

Why build it,
rather than rent it.

Off-the-shelf software is the right answer more often than agencies like to admit. These are the gains that make the other answer worth the build.

  • It follows your process

    A subscription tool makes you adopt the workflow it was designed around, and whatever your business does differently becomes the thing you work around. Software built for you starts from how the work already runs.

  • The manual steps disappear

    Copying between spreadsheets, re-keying an order, chasing a status by email. Every one of those is a handoff, and handoffs are what software is for. Removing them is the plainest return a build has.

  • One record everyone trusts

    Sales, delivery and finance reading the same live record ends the argument about whose export is current. Decisions get made on what is true now, not on what was true when somebody last downloaded it.

  • It changes when the business does

    A new service line, an extra approval step, a rule that applies in one region only. You brief the change and it ships. There is no vendor roadmap to wait on and no feature request to go and vote for.

  • The data and the code are yours

    Your records sit in your own database and come out whenever you ask for them. Nothing is charged per seat for reading what you already own, and a vendor changing its pricing is not a migration project.

  • Customers answer their own questions

    A portal showing order status, documents and history turns your most repeated support email into something people handle themselves, at whatever hour happens to suit them.

When a ready-made tool does the job, we say so. A subscription your team already understands beats a custom build that exists to be custom — the case for building is a process worth keeping, or a cost that scales the wrong way.

Start with a useful
first release.

For B2B and B2C teams, a focused brief makes choices easier. Define the core task before adding more features.

Explore our approach

  1. Name the goal

    Who will use the app? What should they be able to finish? Choose a clear sign that the task works.

  2. Map the essentials

    List the screens, data, and access rules the core task needs. Note which existing tools must connect to it.

  3. Test the whole journey

    Check the path on small screens, with a keyboard, and when something goes wrong. Clear feedback matters as much as the happy path.

From a first release
to real load.

That first release is stage one of four. Each stage answers a question the next one depends on, so you spend on scale when the product has earned it — not before.

  1. Stage 01

    Prototype

    A clickable path through the core task, in front of the people who will use it, before a line of production code is written.

    ProvesThe task makes sense off the whiteboard.

  2. Stage 02

    MVP

    The one journey that matters, built properly: real accounts, real data, a real deployment. Narrow on purpose, finished on purpose.

    ProvesPeople return to it without being asked.

  3. Stage 03

    Product

    The work that surrounds the journey — roles and permissions, reporting, admin tooling, the integrations that end the copy-and-paste.

    ProvesIt earns its place in the working day.

  4. Stage 04

    Scale

    Architecture for load: caching, background queues, read replicas, monitoring with alerts, and a pipeline that ships changes without downtime.

    ProvesGrowth arrives as an opportunity, not an incident.

No application
lives alone.

Your app sits in a business that already runs on other systems. The value is usually in the join: the order that reaches the warehouse without a spreadsheet, the invoice that posts itself.

  • REST and GraphQLA documented API of your own, for your partners and your mobile client.
  • WebhooksEvents pushed the moment they happen, with signed payloads and replay.
  • Scheduled syncNightly reconciliation for systems that will never offer an API.
  • Queues and retriesA failed third party delays a message. It does not lose one.

Payment gateways

Checkout, subscriptions, refunds and dunning, with the card data staying on the provider's side of the line.

ERP and accounting

Orders, invoices and stock moving both ways, reconciled on a schedule your finance team sets.

CRM and sales

One customer record, whichever system someone happens to open first.

Identity and SSO

Sign-in through the directory your client already runs, with access removed the day someone leaves.

Logistics and fulfilment

Rates, labels and tracking pulled in, so status is answered by the app rather than by an email.

Analytics and BI

A clean export into the warehouse your reporting already trusts.

Every integration ships with a sync log your team can read: what moved, what failed, and the button that sends it again.

Where it runs,
and how it is guarded.

Applications that hold customer data are deployed on AWS or Google Cloud, in the region your obligations require, with the boring parts done properly.

  1. Edge

    Delivered close to the visitor

    CDN caching, TLS on every route, rate limiting and a firewall in front of the application.

  2. Application

    Containers that scale with demand

    Stateless services, horizontal autoscaling, health checks and zero-downtime releases that roll back on their own.

  3. Data

    Managed, encrypted, recoverable

    A managed database encrypted at rest, point-in-time recovery, and backups proven by restoring them.

  4. Observability

    You hear it from us first

    Structured logs, metrics and alerts on the paths that matter, so a problem is found before a customer reports it.

Standing safeguards

  • Encryption in transit and at rest, end to end.
  • Least privilege by default, with multi-factor sign-in on every administrative account.
  • Secrets held in a managed vault — never in the repository, never in a build log.
  • Privileged actions written to an audit log that is kept separately.
  • Dependencies and container images scanned on every build, patched on a schedule.
  • Built to support your GDPR obligations: data minimised, export and erasure on request, a documented processor chain, and EU hosting where it is required.

Compliance is your organisation's to hold. Our part is an application that makes holding it straightforward.

Laptop, tablet and phone arranged together on a dark desk.

One app. A wider
business view.

Vermilio brings brand, marketing, and technical work under one roof. Your app should feel like part of your business, from its first screen to its final message.

Tell us who the app is for, what they need to do, and where the current process gets stuck. That is a useful place to begin.

Tell us about your project Need a business website?