Flowstart
Services
WebsiteWeb products built around one business decision.WebshopOnline stores wired to stock, payments and invoicing.Business systemsAI agents and integrations that finish routine work.Customer acquisitionOutbound, chat, voice and follow-up that reach a next step.
WorkInsightsContactMagyar
Book a working session
A laptop with code on the screen
Home/Services/Website

Build the smallest site that answers the decision in front of you.

Prototypes, production sites and platforms, each with a fixed scope, a named owner and a launch number agreed up front. The build matches the decision, the risk and what the operation has to support afterwards.

Discuss a product scopeSee live client work
500architect hours a year returned to BLCD by a site that answers the first question itselfSecondsto a first answer on blcd.hu, previously days
Daysfor a clickable prototype, weeks for a production site
01What you get

A site is worth the decision or transaction it makes possible.

A white modernist building seen from below

BLCD Architects

A ten-page offer sheet became a quote flow that pre-screens buyers.

The site answers the first question and every follow-up in the practice's own words, then hands over a named lead.

500architect hours returned each year

Scope on one page

Users, jobs, constraints, definition of done.

Agreed before the first line of code. Changes go through the same page.

Measured

Launched against a number: sign-ups, bookings or transactions.

A table of laptops and notebooks seen from above

Reviewable increments

You see working slices, not status reports.

Under your ownership

Deployed to infrastructure you control.

  • Your domain, your hosting account
  • Your analytics, consent-gated
  • Documentation your team can run
02Choose the starting point

Match the build to the evidence you need and the operation you must support.

Three sizes. The kickoff call sorts out which one fits the decision, the risk and the budget.

Prototype

Test the user journey before funding a full build.

  • Clickable flows for the target users
  • One focused test of the core assumption
  • Evidence to build, revise or stop

Typically days, subject to scope.

Production site

The version that supports real users, data and transactions.

  • Authentication, payments, data and agreed integrations
  • Deployment to infrastructure under your ownership
  • Measurement and operational monitoring

Typically weeks, subject to scope.

Platform

Extend a proven product with bespoke features and integrations.

  • Custom modules and third-party systems
  • CRM, invoicing or workflow integration where needed
  • An agreed maintenance and support model

Scoped after discovery.

03How delivery runs

Scope, evidence, releases, measurement.

The same four steps on every build, whatever the size.

  1. 01

    Define scope and acceptance

    Agree the users, the jobs, the constraints and the definition of done on one page.

  2. 02

    Prototype the uncertain parts

    Test the riskiest assumptions before committing to the full build.

  3. 03

    Release in reviewable slices

    Deploy agreed pieces so you can judge the working product, not a deck about it.

  4. 04

    Launch against a measure

    Agree the number before release: sign-ups, transactions, completed bookings.

From scope to launch number

Operating flow
01Scope02Prototype03Release04Measure
04Live client work

Review the work in its operating context.

Current client builds, captured from the live sites. Open any of them and judge the product directly.

Open the live site
blcd.hu
BLCD Architects, blcd.huAvena Fitness, avenafitness.huPapersIn, papersin.com
05Selected work

Nine engagements, nine numbers.

All case studies
06What clients said

In their words, after delivery.

Rajmund
“We were answering the same three questions for weeks, usually days after anyone asked them. The site handles that now, and the people who do reach us have already had a real answer.”
RajmundCEO, BLCDRead the case study
Máté Fürjes
“We received a comprehensive SEO audit in 1 day. They worked very precisely!”
Máté FürjesCFO, La Pierre
07Related reading

Notes from the engagements behind this page.

All notes
Method · May 2026 · 3 min read

Start with the workflow, not the model

Tool selection matters, but it comes after the work is understood: trigger, inputs, decisions, ownership, and the result the workflow should improve.

Read the note
Measurement · June 2026 · 3 min read

How to evaluate whether an AI workflow created value

Use an observable process measure before and after implementation: response time, manual effort, follow-up completion, or turnaround time.

Read the note
08Before you book

Questions we get asked first.

Do you build on WordPress or a page builder?

No. We build on Next.js with a database behind it, deployed to hosting you own. Content editing is scoped per project, from a simple markdown workflow to a headless CMS.

How long does a production site take?

Typically weeks, subject to scope. A clickable prototype takes days. The kickoff call gives you a written estimate against a one-page scope.

Can the site connect to our CRM or booking system?

Yes. Integrations are listed in the scope. This site runs on the same stack: n8n behind the forms, Cal.com for bookings, consent-gated analytics.

Who owns the code and the hosting?

You do. The repository, the domain and the hosting account are in your name from day one, and the handover includes documentation your team can run.

What if we already have a site?

Then the first question is whether it needs a rebuild at all. Often the answer is a quote flow, an agent or an integration added to what exists.

Bring the problem your site has to solve.

We will look at the user journey, the scope, the delivery risks, and whether a prototype or a production build is the right next step.

Discuss a product scopeEmail info@flowstart.eu