We build websites. But mostly we write software.
Three lines of custom work. The presentation website is the smallest of them. The other two are programs that someone uses every day — they have their own data, their own users, and their own rules. This page explains how they differ from each other, what is being built in each of them, and what you end up with after launching.
The page is being read. The application is being used.
The difference isn't in how it looks. It's in what's underneath and what it must withstand when someone opens it on Tuesday morning and changes something.
Web
- What's in it
- Texts, photos, contact. Content that describes what you do.
- Who uses it
- Visitor. Comes from Google, reads the page and leaves.
- What needs to be figured out
- Page layout, text, and the order in which they are read.
- What does this follow up on
- Form, map, visitor statistics.
- After launch
- Content is changing.
Application
- What's in it
- Data. Orders, clients, deadlines, inventory — and the rules governing how to handle them.
- Who uses it
- Logged-in users with different rights. Each person sees and changes only what belongs to them.
- What needs to be figured out
- States and exceptions. What happens when an order is canceled, payment fails, or two people click at the same time.
- What does this follow up on
- To the systems you already operate — billing, inventory, payments, sending mail.
- After launch
- The program is changing. Features, people, and data are being added, and the infrastructure must be able to handle it.
Webs
The pages someone finds and reads about you.
Structure, text, photos, contact, and form. Built to load quickly, be readable on mobile, and be understandable to search engines. No underlying logic runs here — and it doesn't need to.
What is being built on this line
- Company presentation
- Web services or product
- Catalog without ordering
- Landing page for campaign
- News, blog, references
- Multilingual version of the same website
What will you have left
An administration where you can change texts, photos, and entire pages yourself. If desired, it can include visitor statistics tracking and integration with Search Console, Analytics, and advertising.
Who does this suit
For companies that expect the website to generate demand and trust. Nothing is calculated within it, and no one logs into it—it's read.
Web applications
A program that runs in a browser and someone works in it every day.
It has its own data, login, permissions, and rules governing its behavior. Nothing needs to be installed—it opens via a link on both computer and phone. It's created just like software, because it is software: first you must decide what information is tracked and what can be done with it, and only then how it looks.
What is being built on this line
-
Ordering system
The customer places an order, you see it come in, change its status, and an email about it is sent out.
-
Reservation and calendar
Free appointments, capacities, confirmations and rescheduling — without copying into a paper diary.
-
Customer Portal
The logged-in client can view their orders, documents, and history instead of having to call.
-
Internal tool for the team
What today holds for the board: documentation, approvals, work plan, warehouse.
-
Custom content system
Custom rules for who writes what, what is visible, and when it is released.
-
Tune in to what's running
Invoicing, warehouse, payment gateway, mail distribution. The data exchange themselves.
What will you have left
Administration of your own data — users, their rights, content, and settings. You can make common changes yourself without needing to modify the program.
Who does this suit
Where today a spreadsheet, email inbox, or paper is making decisions and it's no longer sufficient. Or where a customer should get their own account and stop calling.
Mobile application
A thing a person installs and has at hand even without a browser.
Underneath it is the same work as with a web application — data, accounts, permissions, states — plus things that only a phone can do: notifications, camera, location, and behavior when there's no signal. It's published to the App Store and Google Play, and then maintained, because stores and phones keep changing.
What will you have left
An application released on the App Store and Google Play, along with an administration interface where you populate content and manage users—same as with the web application.
Who does this suit
When the same people keep reaching for the same thing over and over again and want it in their pocket. If all it takes is a website opened in a browser, we'll say so right away.
What is being built on this line
-
Customer application
Orders, loyalty, history, and notifications on your phone instead of in email.
-
Applications for people in the field
Orders, photos from the site, signatures, and notes — even where there's no signal for a while.
-
Web application add-on
Same data and same accounts. In the phone, only what's convenient to have at hand.
-
What only a phone can do
Camera, location, barcode reader, notifications. Things that the browser doesn't do well.
We don't have a finished mobile application in our portfolio yet.
We're building them and offering them, but until there's something out there that you can download and touch, we won't disguise it with a foreign image of a phone. The rest of this page stands on work that is ongoing.
It doesn't end with launching.
No matter which of the three lines we build, it comes with administration where you manage the content yourself. And then it needs to run somewhere: hosting, domain and certificate, database with backups, sending emails from forms and orders, language versions, integration with analytics and advertising.
Our hosting isn't hidden within a single "flat-rate" item. It's broken down into individual components, so you only take what you need, and for each item, it's clear whether it increases with the size of the website or remains unchanged.
Two ways in.
Both start with you describing what you need. What comes back is a design, not an invitation to a meeting.
I want something new
Write what should be created and what it should serve for. Whether it should be a website, a browser application, or a mobile app, we can happily let the requirements guide us — and we'll suggest the smallest reasonable solution for it.
I have a website and I want to redesign it
Send the address. We'll review what's working on it today, what's holding it back — and whether part of what you're currently handling manually should immediately become an application.