Extending existing software and connecting systems

Do you want to add functions, interfaces, a new frontend or a standalone service to an existing system? We deliver the agreed scope and take responsibility for the result.

  • Full-stack experience since 2012
  • Experience with REST and SOAP interfaces
  • Git and SVN, tasks in Jira or your own tool
Diagram: in the middle an application window with six modules, one of them orange; at the top and on the sides six APIs, each marked API with its own symbol (cloud, document, envelope, payment card, chart, company building), the cloud API in orange; at the bottom three databases joined in orange into a cluster

When you need development and integration

Your system should do more, but nobody wants to rebuild it as a whole. Perhaps your team lacks a scarce skill, a process still runs by hand, or your agency has no backend for a client's idea.

We deliver clearly defined work packages:

  • new functions
  • interfaces with SOAP/XML and REST/JSON
  • faster database queries
  • a new frontend for an existing backend
  • a standalone service alongside your system

We work on both frontend and backend.

You work with your own team and want to hand over a defined part, such as the backend for your frontend? See Your team needs support?.

In the middle an existing system with three modules, the new one outlined in orange; around it the typical work packages: a new frontend on top, an interface with a plug to another system on the left, a standalone service on the right and a database with an orange stopwatch for faster queries below

Documents, contracts and PDF as a service

Should your system generate contracts, quotes or forms whose text depends on data and circumstances? We build a dedicated service alongside your software and connect it by API. It works with variables, text variants and rules.

In our engineers' experience, existing document services do produce PDF, but do not always handle variables and case-dependent text variants. Our engineers have programmed such logic before. The technology depends on your environment, for example ColdFusion, Lucee or PHP. We start with a conversation based on a sample document from you.

More on documents and contracts as a service

A small square box with a circle inside, an arrow leading to two stacked sheets with grey lines and two pairs of brackets, one pair filled with orange

API and integrations: typical applications

We provide a function as a service that your system or a new frontend calls. The following applications are examples, not finished products. We define the scope based on your case:

  • Generating PDF and contracts
  • Converting files
  • Integrating systems through SOAP and REST
  • Reconciling data between applications and databases
  • Transactional mail and notifications
  • Document signature workflows: prepare, send, query status
  • Reports for BI and partners

Every service comes with a description of the interface, sample calls and tests with fictitious data. It includes authentication, a log of calls and a description of its behaviour on failure. The code is in your repository.

If an old system itself should become an API, see Use the monolith as a web service.

In the middle a service outlined in orange with curly braces for its interface; on the left an existing system and a new frontend call it; on the right it delivers six typical results: documents, converted files, reconciled databases, mail, signed documents and reports

How a project runs

  1. Clarify the case

    In the intro call you describe the goal and an example: what goes in, what comes out and who calls it. We then estimate the effort.

  2. Build

    We work in manageable packages, report weekly and get in touch before the agreed budget is reached.

  3. Hand over

    You receive the result with documentation and tests. Code and access credentials stay in your repository.

From our projects

  • A phone with a QR code, a file split into chunks, three parallel streams to a server with a disk and a gallery grid

    A photo upload app for wedding guests

    Wedding guests scan a QR code, open one secret address and upload photos and videos straight from the phone: no app, no account, no login. Files of up to 5 GB land on the client's own disk, and the couple watches the gallery fill up during the party. One evening, no second chance, and phones from six years back.

Questions about development and integration

Do you build and integrate APIs (REST, SOAP)?

Yes. We build APIs and connect systems, with REST and JSON as well as SOAP and XML, including the synchronisation of data between applications. Typical use cases are described under Development and integration.

Do you do frontend and backend, or backend only?

Both. Our engineers have worked as full-stack developers since 2012. Typical tasks are a new frontend for an existing backend and the maintenance of jQuery frontends that have grown over the years. For new projects we recommend a front end on Node.js, for example with Next.js and React. We discuss in the intro call whether that suits your system.

Do you work with Jira, Git and SVN?

Yes, with Git and with SVN. We manage tasks in Jira or in the tool you already use. The code lives in your own repository and therefore stays in your hands.

What is your hourly rate?

It depends on scope, engagement model and urgency. Describe your situation briefly and, after a conversation, we will send you an offer. You do not need a budget for that. We quote fixed prices for the entry products.

When can you start?

You will receive a first reply within one working day. When we begin work depends on our current workload and on the scope. We give you a binding answer in the intro call. If it is urgent, the 48-hour emergency assessment starts as soon as we have access to the system.

The first step for documents and contracts: the document pilot

Document pilot

For companies that want to generate contracts, quotes or forms from their system's data, where the text depends on the individual case.

  • One document type, such as a contract or a quote, based on a sample document
  • Variables, text variants and rules for this document type
  • PDF generation through an API that your system calls
  • Tests with fictitious data
  • Assessment of what further document types would need

We agree the scope and price in the intro call and confirm them in writing before we start.

What the result contains

A working service for one document type, with a description of the API, tests and documentation.

In 20 minutes we work out which first step fits your system

You tell us the goal and the current state, and we say openly whether and how we can help. Reply within one working day, no obligation.

Phone (German, Polish, English) +48 501 250 220
Email Email

Reachable: Monday to Friday, 9:00 to 17:00 Central European Time; support and emergencies around the clock (24/7)