WEBISS

How we work

The order does not get rearranged. Every step is here because skipping it has cost money at some point, ours or the client's.

How the work goes

  1. Conversation and questionnaire

    Forty minutes to an hour. We ask the questions and take the notes ourselves, then send a written summary: did we understand it correctly. This is free, and the description of the task stays with you either way, even if we do not end up working together.

  2. The decision: do we take it on

    We answer this before naming a price. There are three outcomes: we take it, we take it with conditions, we turn it down. Conditions are put in writing before the work starts, not after.

  3. The brief

    The task and the measure of success, the scope, what is NOT included, what you provide and by when, the acceptance criteria. Sign-off is written: a spoken «yes, that's right» does not count.

  4. The price

    Only now, and only out of the brief. Subcontractors (photographer, copywriter, designer) and paid services go on separate lines: you can see what you pay us for and what you do not.

  5. Contract and deposit

    A deposit is required. Not so much for the money as for the check on seriousness, on both sides.

  6. Content and build

    You get the content checklist straight away: how many photos, at what size and why, which texts and in which languages. We build the frame in parallel rather than waiting. The deadline is counted from the day the content arrives, and that is written into the brief.

  7. Acceptance

    Against the criteria in the brief, not against a mood, and on a real phone rather than only an emulator: the site does not fall apart on a narrow screen, you can hit the buttons with a finger, the menu works with both a finger and a keyboard.

  8. Launch and handover

    Domain, certificate, analytics, sitemap, Search Console. Access is set up on your accounts, not ours. Plus a short guide on editing it yourself, in your language and with screenshots.

When we turn the work down

We decide this after the questionnaire and before naming a price. Turning it down at that point costs one conversation; turning it down halfway through a project costs money, reputation and months. We refuse plainly and briefly, without apologies and without lecturing, and we say what we think would help you instead of a website.

  • The real problem is not the tool: enquiries already come in but there is nobody to handle them; the product does not sell; the price is off the market. Software does not cure that, and in six months we will be the ones at fault.
  • There is no measurable sign of success, or it is not something software can reach.
  • There are no texts and no photos, no person to make them, and no budget for a photographer and a copywriter. This is the most common reason projects stall. Tested on ourselves.
  • There is no single decision-maker. Three approvers with different opinions make not a project but endless negotiation.
  • The deadline is physically impossible. It must not be promised even under pressure: a missed deadline is worse than a job not taken.

Common questions

Why are there no prices here?
A figure without a scope means either lost money or a conflict at handover. We name the price after the brief, when it is clear what exactly we are doing. This is a position, not a dodge.
How long does the work take?
It depends on the scope, and the honest answer arrives with the brief. One thing can be said in advance: the deadline is counted not from the date of the contract but from the day we received your texts and photos. Waiting for content is the most common reason projects drag on.
What happens after launch?
After two weeks, a short check: does the thing we built it for actually work. After two months we look at the measure written into the brief and say honestly how it turned out. After that, either support (hosting, availability, updates, security, an hour of small edits a month and a short report once a quarter), or we part on good terms. A one-off website ages, and we warn about that in advance rather than afterwards.
Who owns what we build, and the access?
The access is yours and is set up on your accounts: domain, analytics, email. What we build lives on hosting inside our team, with free view access for you; if we part ways, we transfer the project to your team through the standard transfer. The source code stays with us, and that is written into the brief before the work starts rather than surfacing at the end.