1Day · Holiqs x Q-dev

Your product. Built in one day. Without delay.

That idea that keeps coming back.. but never ends up at the top of your list. We finish it in one intensive production day: clearly framed, quick to decide, and at the end stands your developed idea that really works.

1Day visual
  • Tight intake beforehand
  • Production day with direct decisions
  • Working product at the end of the day
  • You remain the owner of the code and environment
1 day full focus 2 perspectives · 1 decision Built on Phlo architecture

What is 1Day?

1Day is not a sprint. Not a workshop. Not a talk day. It is a controlled acceleration: you come with a goal, we deliver a working product on a solid foundation.

Focus over features

We build one core flow that works. Non-essential components are left out of the product day but can be easily added later. This keeps the day fast and the result immediately usable.

Decisions are part of the product

Success requires ownership. Ideally, we work with two stakeholders on the client side, one of whom is a clear decision-maker.

No lock-in, but control

You will get your own environment with dev and production. Maintenance and monitoring can be provided optionally.

Imagine...

We do not label on "website", "webshop" or "AI". We start with recognizable situations so that you can immediately feel: this could be my product.

!
!

"This can be better"

A platform, process, or tool that you have been annoyed with for too long. We build a sharp, usable variant for one niche or one goal.

  • Niche question-and-answer platforms
  • Alternatives to bulky software
  • Fast, goal-oriented portals
Start the intake
M
M

"I'm doing this manually now"

Processes that live in emails, Excel, or heads. We create a system that people understand and want to use.

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

"I have an idea"

Testing something, showing it or using it internally. No endless roadmap. A v1 that actually works.

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

"I want this for myself"

Not everything has to be a business right away. Sometimes you just want something that doesn't exist yet but 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 internal politics
  • xEverything-must-be-in programs without choices

This is how the product day goes

Calm in design, strict in choices, built to force progress without stress.

1

Intake & scope-check

We determine the core flow and clear 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 build. You decide. Together we bring your product to life.

3

Delivery & transfer

At the end, there is a working product. You will receive access, explanation, and a clear follow-up path.

Game rules (short)

  • Two perspectives on the client side is ideal, with one decision-maker
  • When in doubt, we choose the simplest working solution
  • Discussion is allowed, stagnation is not
  • "Later" protects the scope, no failure

What you have at the end of the day

No presentation. No promises. A working product on a foundation that can be built upon.

Working core flow

The essence is there. Not everything included, but exactly what you need to use, test, or showcase.

Dev/prod basis

A neat development street is possible, allowing you to iterate and build safely without chaos.

Connections that work

Email, webhooks, WhatsApp or other integrations. Only what the core flow really needs.

Ownership

Code, data, and environment belong to you. Period. No lock-in, no surprises afterwards.

Basis for growth

Not a disposable prototype, but a foundation that remains expandable as you accelerate.

Clear next step

After 1Day, "version 2" is concrete. You know exactly what the next desired iteration is.

Your idea here

This block is still empty and waiting for 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 momentum: 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 easily learn to build on your product yourself? We can teach you that too, even with minimal background knowledge.

FAQ

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

That is why we conduct a strict intake. If we doubt whether 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 remains: one sharp scope, one functioning core flow.

Isn't this just "vibe coding"?

No. We certainly use AI as a tool in the construction process, but the product does not rely on AI as a foundation. We build on a strong, thoughtful architecture in which AI is a catalyst and not the basis.

Who owns the code and data?

You. After delivery, the product is yours. We prefer to build your own environment, so you are not stuck in 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 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 be honest about it and provide a more realistic alternative.

Ready to create something real?

Start the intake. We will honestly assess whether your idea fits within a product day.

Start the intake
Intake

Does your idea fit in 1Day?

We use your application to clearly determine if this is suitable for one product day.

We usually respond within 1–2 business days.

What you receive after the intake

  • A fair scope check: does this fit in 1Day or not?
  • Where necessary, some probing questions for 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 sharp choices. The intake is part of the speed and quality of the final product.