Skip to content
Telegram[email protected]
JVD
uk
Services

Websites and web products end to end — from mockup to release.

One contract, one team, one line of responsibility. Design, code, database and server are all ours, so there is no «that is not our side» and no week spent waiting on someone else's contractor.

Websites and landing pages

A corporate site, a landing page or a multilingual catalogue, built so search engines can see it and the client — not a developer — edits the copy.Prototype, design, markup, a CMS for text and imagesSEO frame: semantics, schema.org, sitemap, llms.txt, fast LCPAnalytics, forms, CRM integration
from [amount]
2–4 weeks
What is included
  • A prototype of every page before any design work
  • Responsive layouts for 1440 desktop and 390 mobile
  • A two-language admin panel for every string and image
  • Technical SEO: canonical, hreflang, Open Graph, JSON-LD
  • An enquiry form with antispam and email plus Telegram alerts
  • Deploy, domain, HTTPS and database backups
How it runs
  1. 01

    Understanding the job

    We ask who you sell to and what makes you different. Out comes a page structure and a list of what must be indexable.

  2. 02

    Prototype and design

    A grey prototype first, design second. Changes cost nothing on a prototype and a lot on built markup.

  3. 03

    Build

    Server-side rendering so crawlers get finished HTML. Real copy goes into the admin panel as we go.

  4. 04

    Launch

    We check speed, structured data and links, wire up analytics and hand over the credentials.

What you get

A site that loads in about a second, serves crawlers finished HTML in both languages, and has an admin panel where your content person changes copy without us.

Examples
jvdsoft.com

The company's own site: SSR, two languages, every marketing string editable in the admin, a status page with live probes.

JVD Soft →
Get an estimate

SaaS products

A product with subscriptions, roles and an API — from the first version to infrastructure that survives a second instance.Auth, roles, billing and subscriptions, admin panelAPIs, webhooks, queues, background jobsInfrastructure, CI/CD, monitoring and alerts
from [amount]
6–10 weeks
What is included
  • A data model and migrations you can run against production
  • Auth with token rotation and lockout after failed attempts
  • Roles enforced on routes, not on buttons
  • A job queue and an outbox so a dead SMTP host cannot lose a lead
  • Prometheus metrics, error reports, a status page
  • CI: lint, types, tests and a build on every push
How it runs
  1. 01

    Model and boundaries

    We agree what an account, a subscription and a limit are. Cheaper to change on a whiteboard than in migrations.

  2. 02

    Vertical slice

    One complete feature from database to screen, with tests. Everything after it follows the same template.

  3. 03

    Billing and roles

    Subscriptions, limits, roles. Idempotency and the audit log land here, because money does not forgive retries.

  4. 04

    Operations

    Monitoring, alerts, backups with a restore test, zero-downtime deploys.

What you get

A working product you can show investors and first customers, with a predictable cost of change: a new feature is a vertical slice, not a rewrite.

Examples
Qrenza

A catalogue and QR menu with real-time ordering: multilingual, a venue admin panel, public pages built for search.

Qrenza →
ShiftPlan

Shift planning for teams: roles, shift swaps, notifications. It replaces spreadsheets in companies of 20–200 people.

ShiftPlan →
Get an estimate

Internal systems

A tool instead of a spreadsheet, where you can see who changed what, and which does not break when the company doubles.Replacing spreadsheets and notebooks with a real toolRecords, reports, access rights, change historyMigrating the data you already have
from [amount]
4–8 weeks
What is included
  • An audit of the current process — what people actually do, not what the policy says
  • Roles and permissions mapped to real job titles
  • Change history and an audit log: who, what, when
  • Data import from Excel, Google Sheets or the old system
  • Reports and CSV export
  • Training and a manual written in the user’s language
How it runs
  1. 01

    Observation

    We watch how the work happens today. Half the "requirements" disappear once you see a real working day.

  2. 02

    Pilot on one team

    We launch with one department while the old spreadsheet is still alive. Zero risk.

  3. 03

    Data migration

    We move the history and reconcile totals against the old numbers. Without that nobody trusts the system.

  4. 04

    Rollout

    The remaining departments, access rights, management reports.

What you get

One place where the data lives, with access rights and a change history. Reports that used to take half a day now build in a second.

Get an estimate

Integrations and support

We stitch your systems together and take over code somebody else wrote.Payments, delivery, ERP, Telegram bots, third-party APIsTaking over someone else's code: audit, stabilisation, documentationMonthly support with an agreed response time
from [amount] / mo
by agreement
What is included
  • An audit of the existing code with a written report and a risk list
  • Integrations with signed webhooks and retries on failure
  • Idempotency on anything that moves money
  • Monitoring of third-party services and alerts when a partner API goes down
  • An agreed response time and maintenance window
  • Documentation good enough to replace us with
How it runs
  1. 01

    Audit

    We read the code and look at logs and databases. Out comes a report: what works and what is held together by hope.

  2. 02

    Stabilisation

    First we stop the bleeding and add monitoring. New features come after that.

  3. 03

    Integration

    Third-party systems are called through a retrying queue, not straight from a user request.

  4. 04

    Support

    A monthly cycle: a task queue, an agreed response time, a report on what was done.

What you get

Systems that exchange data without a manual export, and a team you can message when the payment gateway falls over at six in the morning.

Get an estimate
How a project runs
Conversation and estimate

An hour on a call, a week for the quote and the plan. Free.

Prototype

Clickable screens that show the product before a line of code is written.

Development in sprints

A demo every two weeks, access to the task board and to the code.

Release and support

Deploy, monitoring, a 6-month warranty on the code, then support.

Contract and NDA

We work formally, with fixed scope and dates. The NDA is signed before the first detail.

The code is yours

Repository, access and infrastructure are in your name from day one. No lock-in.

6-month warranty

Bugs in our code are fixed free of charge. New features are quoted separately and openly.

Tell us what you need — we will work out the rest.

We answer within two hours on a working day and come back with an estimate and a quote inside a week. If the job is not for us, we will say so and point you to someone better suited.

Get an estimate