Integrations
Payments, shipping, accounting, marketplaces, CRM. We check that data flows both ways and survives updates, beyond the fact that it connected.
People come to us for website development with one of three requests: they need a first website, they need to replace the one they have, or they need someone else's work finished. The sections below are split along exactly these lines, because the answer shapes everything else: the scope, the timeline and whether starting from scratch makes sense at all. The most expensive mistake here isn't technical. It's ordering something big where a simpler build would do, or rewriting a site that only needed improvements. So each page below describes what is included and also where the limits are: when an option fits and when another one is the better choice. We calculate the cost after a free review, because before that any figure would be made up.
We define what the site must do, which pages and data it needs, and what it has to connect with.
Catalog, cart, payment, delivery and your accounting service are put together into one working system.
Before launch we test buyer scenarios; after the act, the domain, hosting and code belong to you.
Scope and timing depend on the task and the number of integrations. We give an estimate by stages after a brief or an audit, not upfront.
Payments, shipping, accounting, marketplaces, CRM. We check that data flows both ways and survives updates, beyond the fact that it connected.
Online store development, from a niche catalog of a few hundred items to a large one with tens of thousands. Tasks by niche, sales model, and platform.
Subscription services, internal systems, a first version to test an idea. The real question is what has to work in version one, not which tech to use.
New features, taking over another developer's project, fixing a previous contractor's work. We tell you plainly when a rebuild would cost less.
Corporate websites, landing pages, multilingual catalogs. The type of site is set by what has to happen after launch, more than by the budget.
The main decision here is the type of site, not the design: a business card site, a landing page, a catalog or a store. They differ less in budget than in where people come from and what they need to do. The Websites section is organized around exactly that; stores have a section of their own, because there the question starts with the catalog.
We'll review your situation in a free auditFeatures are missing, the catalog is updated by hand, the platform is outdated. That isn't always a reason to rewrite from scratch, and improving the existing site is often cheaper. Which case is yours becomes clear after we review the code, and that's the first thing we do.
Payments, delivery, accounting, marketplaces, CRM. Every such link is a separate point of failure, and the job here is less about connecting than about checking that data flows both ways and nothing breaks after updates.
A subscription service, an internal system instead of twenty spreadsheets, a first version to test an idea. This is a different construction: a website informs, an application does the work, and it is designed around the user scenario rather than the pages.
We clarify the task and tell you what it needs: a new site, improvements to the existing one or a different solution altogether. This is also where it becomes clear which of the four sections to start with.
We state the scope, the timeline in working days and the price broken down by stages, then put it in writing. The acceptance procedure and warranty go into the contract too, instead of living in chat messages.
We build the project in parts and show the result on a live environment. You see how it really looks and can still change direction while a correction costs only a conversation.
We move the site to your hosting, hand over access and documentation, and sign the acceptance act. From that day, the 30-calendar-day warranty on the completed work applies.
These figures come from case studies on live sites: what was measured, when, and where it can be seen, with the measurement method described in each case.
With a review of the task: it's free and takes one to three working days. You describe what needs to happen in your business, and we tell you which solution covers it. Quite often the answer is cheaper than expected: improving the current site instead of building a new one, a catalog without a cart instead of a store.
Because the scope of work with the same name differs several times over between two clients, and a "starting from" figure would be misleading. The process goes like this: first a free review, then an estimate broken down by stages, then a contract with a fixed price. That way you know the final figure before work starts, not after.
Yes, for every project. The contractor is a registered Ukrainian sole proprietor (FOP), and payment goes to a bank account with full closing documents. The contract fixes the scope, timeline, price and acceptance procedure; the result is handed over under an acceptance act, and a 30-calendar-day warranty applies from the day it is signed.
You will. Property rights to the code, design and materials pass to the client after full payment. We register the domain, hosting, repository, analytics and ad accounts to you right away, not at the end, so that changing contractors never means losing the project.
The timeline is driven by scope more than by complexity: the number of pages, the number of integrations and whether the content is ready. So we give a figure after the review and count it from the moment access and materials are available, not from the contract date. This matters in practice: the most common reason for delays is waiting for copy and photos from the client rather than development itself, and no number of people on the project changes that.
Yes, taking over a project is a separate type of work in the improvements section. It starts with an inventory instead of code: what access exists, what state the code is in and which of the promised features were actually built. After that we tell you directly whether to improve or rebuild, even when staying quiet would pay us better.
Your task goes straight into work, with no account managers and nothing relayed through third parties, and the project isn't handed to someone else midway. Response time is two hours during business hours. That's what you will see in practice; other details of how the work is organized make no difference to the result.
A few sentences are enough: what you sell, who your buyer is and what a visitor should do on the site, whether that's calling, leaving a request or buying. If you have examples of sites you like or find annoying, include them: that saves a day of clarifications. You don't need to write a technical specification. During the free review we ask the questions ourselves and come back with a structure and a list of pages. Copy, photos and company details will be needed later, and how ready they are most often determines the timeline.
LIONEX AI First Agency is an agency by name and, legally, a registered sole proprietor (FOP): a contract for every project, payment to a bank account, closing documents. What matters more to you is how this looks in practice. Your task goes straight into work, with no account managers and nothing relayed through third parties, and the project isn't handed to someone else midway. We respond within two hours during business hours. Commercial development since 2015, 53 projects in the portfolio, 33 of them online stores.
Describe the task in your own words — we will tell you where to start and whether you need what you came for. If you do not, we will say so.