1Day · Holiqs

Your product. Built in one day. Really.

That idea that has been in your head for months, but that you never make time for. We finish it in one production day: tightly framed, decisive, and at the end there is something that runs.

Start the intake See the magic
1Day visual
  • Tight intake beforehand
  • Production day with live decisions
  • Working product at the end of the day
  • You are the owner of the code and environment
1 day focus 2 perspectives · 1 decision Gebouwd op Phlo-architectuur

What is 1Day?

1Day is not a "sprint" and not a workshop. It is a controlled acceleration: you bring a goal, we deliver a working product on a solid foundation.

Focus over features

We build one core flow that works. Everything that is not essential goes to "later". This makes the day quick and the result usable.

Decisiveness is part of the product

The customer is a co-owner of success. We prefer to work with two stakeholders on the customer side, with one final decision-maker.

No lock-in, but peace of mind

You will get your own environment with dev/prod. We can also provide maintenance and monitoring.

Imagine...

We do not position ourselves on "website / webshop / AI". We position ourselves on recognizable situations so that you immediately feel: this could be my product.

!
!

"This can be better"

A platform, process, or tool that you find annoying. We are building a sharp, usable variant for one niche or one purpose.

  • Niche marketplaces
  • Alternatives to bulky software
  • Fast, goal-oriented portals
Start the intake
M
M

"I'm doing this manually now"

Things that currently exist in emails, Excel, or people's heads. We create a system that people understand and dare to use.

  • Admin tools and dashboards
  • Intake and decision flows
  • Customer portals and status overviews
Start the intake
I
I

"I have an idea"

You want to test something, show it, or use it internally. No endless roadmap, but a v1 that really works.

  • MVPs and niche SaaS
  • Tools for a target audience
  • Specific integrations and automation
Start the intake
Y
Y

"I want this for myself"

Not everything needs to be a business right away. Sometimes you just want something that doesn't exist yet and that works well.

  • Personal tools
  • Hobby or community systems
  • Creative or technical prototypes
Start the intake

Who is this for?

  • 1People with a concrete goal and decisiveness
  • 2Entrepreneurs who want something real, not "someday"
  • 3Teams that need a specific tool or flow

For whom not?

  • xIdeas without an owner or decision-maker
  • xProjects with long political decision-making
  • xEverything-must-be-in programs without choices

This is how the product day goes

Calm, tightly framed, and built to enforce decisions without stress.

1

Intake & scope-check

We determine the core flow and the boundaries in advance. If we doubt whether it fits in one day, we do not schedule it.

2

The production day

You are involved. We discuss, we build. You decide how your product looks and works.

3

Delivery & transfer

At the end, there is a working product. You will receive access, transfer, and a clear path for any further development.

Game rules (short)

  • Two perspectives on the client side is ideal, with one decision-maker
  • In case of doubt, we choose the simplest working solution
  • Discussion is allowed, stagnation is not
  • "Later" is not a failure, but scope protection

What you have at the end of the day

Not a pile of ideas. A working product, on a foundation that can grow.

Working core flow

A working product, not with all features but with everything you need at that moment.

Dev/prod basis

We can set up a clean development pipeline so you can build safely.

Connections that work

Email, webhooks, WhatsApp or other integrations that the product really requires.

Ownership

You remain the owner of code, data, and environment. No lock-in.

Basis for growth

Not a throw-away prototype, but a foundation that remains expandable.

Clear next step

After the day, you will know exactly what "version 2" is, without any doubt.

Your idea here

This block is still empty. Fill it with your plan.

Start the intake

The deal: scope and responsibility

Definition of done

At the end of the product day, there is a working product, (online) accessible, with a clear core flow.

  • We agree in advance what is and isn't included
  • If we run out because of our debt, we finish it without hassle
  • You get access and transfer
  • Content (text/images) should ideally be available in advance

What we need from you

  • B

    Decisiveness

    Two stakeholders is ideal, with one decision-maker. Without a decision-maker, we do not plan.

  • F

    Focus

    We build one core flow. Park extras where needed for later.

  • A

    Assets

    Logo, colors, texts, and examples accelerate enormously. No assets? Then we build clean or use the day for design.

Investment

You don't buy hours, but focus, experience, and acceleration on a foundation that can grow.

1Day

The product day

Fixed price based on scope

We determine in advance what is feasible and agree on a fixed price. No surprises afterwards.

Start the intake

Included

  • 1 day execution (construction + direction)
  • Live decision-making with you
  • Delivery + transfer
  • Short aftercare
Optional

Product Care

Rust after delivery

For customers who want to run their product on a clear own infrastructure, with monitoring, periodic checks, and updates.

Typically included

  • Uptime monitoring
  • Periodic technical checks
  • Security updates (OS/runtime)
  • Backups & basic control

Product Care is not feature development. It is protection and continuity.

Do you want to learn to build on your product easily? We can teach you that too, even with minimal background.

FAQ

What if it's not finished by the end of the day?

That is why we conduct a strict intake. If we doubt that it fits within one product day, we do not schedule it. If we run over due to our fault, we will resolve it properly.

Is this only for websites?

No. It can be a website, a tool, a dashboard, an AI flow, an integration, an app, or something very specific. The core is: one sharp scope, one functioning core flow.

Isn't this just vibe coding?

No, we do use AI in the building process, but we specifically build on a strong architecture so that AI is an addition and not the foundation.

Who owns the code and data?

You. After delivery, the product is yours. We prefer to build your own environment, so you are not squeezed by lock-in constructions.

Does this need to be at your location?

No. It can be at our place in the Amsterdam region or at your location, or even at another suitable collaboration location. On-site works well if there are multiple stakeholders and quick decisions are needed.

How do I know if my idea is suitable?

Fill in the intake. If it fits, we will schedule a short scope call. If it doesn't fit, we will say so honestly and provide a more realistic alternative.

Ready to build something real?

Start the intake. We will assess whether your idea is suitable for a product day.

Start the intake
Intake

Does your idea fit in 1Day?

We use your application to determine if your idea is suitable for a product day.

We usually respond within 1–2 business days with a Go / No-Go and possibly a short scope call.

What you receive after the intake

  • A fair scope check: does this fit in 1Day or not?
  • If it fits: a short call to establish the Definition of Done
  • A fixed price proposal based on scope
1 day focus Scope protected Ownership

Why so strict?

Because this only works with clear choices. The intake is part of the quality of the final product.