Skip to main content
webforte

Custom web application and software development

When a business runs on spreadsheets, email and retyping between systems, every job drags. Our web application development starts from how you actually work. It connects to your accounting, e-shop or CRM, and the code and data stay yours.

  • Code in a repository you have full access to
  • Integrations with Pohoda, Money S3, ABRA Flexi and Fakturoid
  • 4 own applications running in production

Custom web applications at a glance

Custom web application and software development is the design, programming and operation of software for a specific company process: job tracking, purchasing, a client portal or the first version of your own SaaS product. Webforte Technologies s.r.o. (company ID 23364343, Prague) builds web applications that run in the browser and connects them by API to Pohoda, Money S3, ABRA Flexi, Fakturoid, e-shops and CRM. Where it helps, it adds AI. It builds with Next.js, TypeScript and PostgreSQL, runs applications in Docker on a VPS or the client's server, and the client owns the code and data. Webforte also runs its own applications Dotazio, Kurikula.ai, Chytrej článek, Chytrejbyt.cz and Chytrej dárek. Pricing follows a quote after a consultation. We communicate in English.

When spreadsheets and off-the-shelf software stop being enough

The same job twice: in a shared spreadsheet and in a web application. The numbers match the pairs below.

  1. Today

    Excel is used as a database

    Jobs, stock or attendance live in a shared spreadsheet. Two people edit the same row, a formula breaks and nobody knows which version is right.

    In the application

    One database with a change history

    Every record exists once. The application controls who may change what and logs who made each change and when.

  2. Today

    Data is retyped between systems

    An order arrives by email, someone copies it into a spreadsheet, then into accounting and finally into the e-shop. Typos only surface on the invoice.

    In the application

    Enter it once

    The application passes the data to Pohoda, Money S3 or Fakturoid through the API and reads the invoice status back. Nobody retypes anything.

  3. Today

    Off-the-shelf software does not fit your process

    A ready-made system has plenty of features, just not the one you need. Exceptions end up in yet another spreadsheet next to the program.

    In the application

    Steps that follow your process

    We design screens, statuses and approvals around how your company actually works. When the process changes, the application is adjusted, not the people.

  4. Today

    Information is scattered across inboxes

    Only the person with the email knows the status of a job. When they are away, everything has to be pieced together from emails and phone calls.

    In the application

    Anyone with permission sees the status

    Comments, attachments and deadlines sit with the job. A colleague can take it over without searching someone else's inbox.

What custom software we build

Most often a web application: software that runs in the browser, where people sign in and work with data. Five types and what they usually include.

Internal systems and records

The replacement for the shared spreadsheet: records of jobs, production, stock, service or attendance. The application knows your statuses and rules, watches deadlines and alerts you when something gets stuck.

  • Jobs and their status from enquiry to invoice
  • Stock, issue slips and stocktaking
  • Service and warranty claims

What a custom web application is made of

Underneath the screen are layers that decide whether the application lasts for years and can connect to other systems. We go through each one during design.

  • Interface for your team and clients

    An admin area for your staff, a portal for customers or both. It runs in the browser on a computer or phone, and each role sees only what it needs for its work.

    • Admin area for your team
    • Client portal
    • Computer, tablet and phone
  • API (application programming interface)

    Every request from the screens goes through the API to the database and to other systems. It checks who is signed in and what they may do, validates the input and records the change.

    • Roles and permissions
    • Input validation
    • Change history
  • Integrations with your systems

    Data is passed on automatically through the interface the system's vendor officially provides.

    Pohoda
    XML, mServer
    Money S3
    API module, XML
    ABRA Flexi
    REST API
    Fakturoid, iDoklad
    API v3
    Shoptet, WooCommerce
    REST API
    Pipedrive, HubSpot, Raynet
    REST API
    How the integrations work
  • Only where it helps

    AI layer

    An AI agent that prepares documents or sorts requests, and extraction of data from invoices and contracts. The output is checked by a rule or a person before it is written to the database.

    • Document extraction
    • AI agent
    • Search across documents
    AI agents inside your systems
  • Database

    One place for the data instead of several versions of a spreadsheet. We use PostgreSQL, migrate the data from your old spreadsheets and set up backups to match where the application runs.

    • PostgreSQL
    • Migration from Excel
    • Backups to match hosting

We build with Next.js, React and TypeScript on a PostgreSQL database. The application runs in Docker on a VPS or on your server.

Talk the architecture through

Off-the-shelf software, no-⁠code or custom application development

A custom application is not always the right answer. If ready-made software covers your process, we will recommend it.

Swipe the table sideways to see all columns.

Off-the-shelf software, no-⁠code or custom application development
Off-the-shelf software, no-⁠code or custom application developmentOff-the-shelf softwareNo-⁠code toolCustom application
What it isA ready-made program for common tasks, you pay for a licenceAn application assembled without programming on someone else's platform, such as Airtable or GlideSoftware designed and programmed for your process
Fit with your processThe process adapts to the programWithin the limits the platform allowsThe application adapts to the process
Integration with accounting, e-shop, CRMOnly ready-made connectors, if they existPlatform connectors, more complex rules hit limitsThrough APIs, following your rules
Running costsLicence, usually per userPlatform subscription, often by users or recordsHosting and maintenance, no per-user fee
Where the data livesDepends on the program: in the vendor's cloud or on your own computer or serverOn the provider's platformIn your database, on a server you choose
Best whenIt is a standard task: accounting, payroll, invoicingA small team needs a simple overview or formYour process is your advantage, or nothing ready-made fits

We often combine them: accounting stays in Pohoda or Money S3 and the custom application covers what the boxed software cannot. A no-⁠code tool is a good way to test a process before investing in development.

Five steps from process map to operation

Each step ends with an output you decide on. We build a large application in parts, so your team can use the first part before everything is finished.

  1. Consultation and process map

    We go through how a job or order moves through your company today, who works on it, which spreadsheets and systems hold the data and where time is lost. We also tell you when ready-made software is enough.

    OutputProcess description and a non-binding quote

  2. Screen and data design

    We design the screens, roles and permissions, the data model and the list of integrations. The design shows whether the application fits the real work before the first line of code is written.

    OutputDesign of screens, roles and integrations

  3. First version

    We build the core of the application around one main process (an MVP). Your team tries it on real data and we adjust whatever gets in the way.

    OutputAn application your team starts using

  4. Integrations and data migration

    We connect accounting, e-shop or CRM through their APIs and migrate the data from old spreadsheets. We agree in advance which system is the master for each piece of data.

    OutputData in one place, connected systems

  5. Deployment, handover and operation

    We deploy in Docker on a VPS or on your server, set up backups, train your team and hand over the code in a repository, the database with your data and the access. After that we look after updates and security and add features based on use, or hand everything to your developer.

    OutputA running application; code, data and access are yours

When a custom application pays off and when it does not

It makes sense when

  • You have a recurring process currently held together by spreadsheets, emails and people's memory
  • You have tried ready-made programs and something essential for your operations was always missing
  • You need to connect systems that do not talk to each other, such as accounting and an e-shop
  • You want to own the code and data and have an application that can grow with the business

It does not make sense when

  • Ready-made software or a no-⁠code tool covers your process and suits you
  • The process is still taking shape and changes every week: try it in a spreadsheet first
  • Nobody in the company has time to help with the brief and testing
  • What you mainly need is a website that brings enquiries: web design is enough for that

Frequently asked questions

The price depends on scope, so we do not publish a price list. The biggest factors are the number of screens and processes, roles, integrations with other systems, migrating data from old spreadsheets and AI features, where model usage is paid for too. A cheaper route is a first version (MVP) that solves the costliest problem. We prepare a non-binding quote from your process description and list of systems.

A single-process application takes weeks; a system with several roles and integrations takes months. So we build in parts: the first version covers the main process and your team starts using it while the next parts are built. The schedule depends most on how fast we get access to the connected systems and feedback from users. A concrete schedule is part of the quote.

A web application is software that runs in the browser: users install nothing, sign in and work with data stored in a database on a server. A website mainly informs and leads to an enquiry; an application is for working with roles and data, such as orders or bookings. If you mainly need a presentation and enquiries, a website is enough.

You do. We hand over the source code in a repository you have full access to, and the data stays in your database. The application is built on open-source technology (Next.js, React, PostgreSQL) with no per-user licences, so your own developer or another company can continue developing it. The documentation describes the data model, roles and integrations.

Yes. We connect Pohoda through XML, by file exchange or through POHODA mServer. Money S3 has an API extension module for continuous reading and writing; without it XML exchange remains. ABRA Flexi has a REST API, Fakturoid and iDoklad an API v3. Before we start we check your licence and modules, because some interfaces need an extension on the accounting software side.

Next.js and React with TypeScript, with data in PostgreSQL through Drizzle ORM. The application runs in Docker on a VPS or on your server, depending on where the data may live. We set up backups to suit the hosting, and we can keep running it or your IT can take over. These are widespread open-source technologies, so you can find other developers.

Yes, where it has a clear job: extracting data from invoices and contracts, sorting incoming requests, searching company documents or an AI agent that prepares documents. For every AI feature we decide in advance where a rule or a person checks the output, and we discuss running costs, because model calls are paid by the volume of text processed.

We expect it to. A custom application is adjusted as your operations evolve: you add an approval step, a new role or an integration, and only what needs to change is changed. That is why we build on a clear data model and hand over the code with documentation. Further development can be done by us or by your developer.

Let's talk through your case.

Describe the process that slows you down and the systems you use. In a consultation we go through it, tell you whether a custom application, ready-made software or an adjustment of what you already have makes sense, and prepare a non-binding quote. We communicate in English.

Free consultation