Full-cycle services

From landing pages to online banking. One team owns the whole cycle — strategy, design, engineering, launch and growth. Pick a direction.

We cover the whole cycle: research, design, engineering, launch on a server and support after release. One team owns the result — no middlemen and no passing the blame. Below are the directions we work in; each has its own page with scope, stages, timelines and price.

Ikat. Steel wire

IT assurance and managed IT

Beyond development, two lines on the customer’s side: independent assurance of other vendors’ projects and an IT department for private business.

Solutions with a price

If you already know what you need built: price, timeline and scope on a single page.

All prices

Where to start when the direction is not chosen yet

The name of a service rarely matches the way a person phrases the problem. Below it is arranged by problem, not by catalogue section.

You need to explain the product and collect enquiriesA landing page or corporate site: the first screen, the offer, forms, analytics, speed. This is where you start when the product exists but the storefront does not.The company runs on spreadsheetsA CRM or ERP shaped around your processes. Rewriting a process into a system is usually cheaper than hiring people to reconcile spreadsheets by hand.The product must work in your customer’s pocketiOS and Android. With one budget and two platforms we start where the money is and port to the second once demand is proven.Money, payments, compliancePayment and banking systems: idempotent operations, reconciliation, audit logs, KYC/AML. That is separate engineering, not “a site with a pay button”.Plenty of data, no decisions coming out of itAnalytics and models: from an honest reporting layer to assistants that work with your own documents.Things fall over, releases are scary, the cloud bill growsInfrastructure and DevOps: zero-downtime deploys, monitoring, rollbacks, cost under control.The product exists but is awkward to useProduct design: flows, interface, design system. Often worth more than another batch of features.You need a place where sellers meet buyersA marketplace: catalogue, search, settlements between parties, disputes and moderation.Your customers live in messengersTelegram and WhatsApp bots, Mini Apps: ordering, booking, payment and support where the person already is.Someone else wrote the system and it has to growSupport and evolution of inherited code: audit and stabilisation first, changes after. Sometimes a rewrite is the better deal — and we say so before work begins.You have an idea and need to test it on the marketAn MVP: a prototype validated with customers in three weeks, a first version with payments in eight. You pay to test the idea, not for a product nobody needs.Equipment and sites must be monitored and controlled remotelyIoT: sensors, a real-time dashboard, alerts and remote control. Greenhouses, warehouses, cold storage, factories.A restaurant, clinic, school or retail chainIndustry solutions: delivery and QR menus, booking and patient records, online schools, loyalty, kiosks, dealer portals. The foundation is ready — you pay for what makes you different.

What every engagement includes, whatever the direction

This is not a service list but an engineering minimum. It is the same for a landing page and for a payment core — only the depth changes.

Architecture before code

Decisions about structure, data and system boundaries come first, lines of code second. Rewriting a document is cheaper than rewriting a service.

Readable code and review

Code is read more often than written. We write so that a year from now someone who did not write it — including your future developer — can work with it.

Checks before deployment

Types, linting, build and automated checks run before a change reaches production, not after a user complains.

Deploys that can roll back

A new version is built next to the running one and swapped in instantly. If it does not respond, the previous one returns automatically.

Monitoring and error tracking

A system must report its own failures. Learning about a breakage from your customer is the most expensive option.

The code is yours

Sources, access and documentation are handed over. We do not keep you hooked on infrastructure you cannot take with you.

What it costs

There is no single price “for a website”, and an average delivery time is fiction too: a landing page and an online bank differ by an order of magnitude. That is why the configurator is public: it computes a range, a timeline and a team shape from your parameters — no briefs, no waiting.

Product type

Landing page, corporate site, SaaS, mobile app, store, fintech, marketplace — different systems, different engineering.

Scale

An MVP to test demand, a working version, or a system built for load and resilience.

Design

Template, custom, or award-submission level — this affects the timeline as much as functionality does.

Modules

Payments, roles and permissions, integrations, multilingual support, analytics, chat — each adds both cost and time.

Speed

Acceleration is possible but it costs money: parallel teams are more expensive than sequential work.

A precise estimate follows a thirty-minute conversation and commits you to nothing. The configurator gives an honest order of magnitude before it.

Ways to work together

Three ways to start. The choice depends on how well defined the problem is.

Fixed-scope project

When the task is clear and a result is needed by a date. Fixed scope, staged acceptance, warranty on the code after launch.

Product development

When the product lives and changes. The team works in sprints, priorities are revisited, releases are regular.

Support and stewardship

When the system runs but somebody has to own its health: monitoring, updates, fixes, a plan for what comes next.

Frequently asked

How does the work start?

With a thirty-minute conversation about the problem — no deck, no obligation. After it we come back with a range, a timeline and a plan for the first steps. If the task is not for us, we say so straight away.

How long does development take?

It depends on the product: a landing page from two weeks, a corporate site from a month, a first version of a SaaS or mobile app two to three months, a full product about four, a fintech system four months or more. The configurator computes the timeline from your parameters.

Who owns the code?

You do. Source code, access and documentation are handed over to the client. We keep no infrastructure without which the product stops working.

What happens after launch?

Defects in code we wrote are fixed free of charge, with no expiry date. Ongoing development and infrastructure support are agreed separately — but the product is never left abandoned.

Do you work with someone else’s code?

Yes, starting with an audit. Sometimes the honest answer is to rewrite, and we say it even when patching for months would pay us better. The decision is always yours, but taken with the numbers in the open.

What about confidentiality?

The NDA is signed before the first substantive conversation. White-label work is routine: you are free not to name us as the contractor.

What backs this up

Every promise on this page is backed by a document you can open and check. Three sections that show how we work from the inside.

Where to start

Not sure which direction fits

Describe the task in plain words — we’ll propose an approach and tell you straight if it can be solved simpler and cheaper than you expect.

You need a budget and timeline

Configure the project in the configurator: price, timeline and team are calculated live, with no briefs and no waiting.

The product already exists

We’ll take it on for support and growth — ours or inherited — starting with an audit and a quarterly plan.

Build your project in the configurator →