Delay that cascades
The supplier slips a week, you slip your client by two, and you lose control of your schedule. Here the date is set before we start, and if it moves you are told before the deadline, never after.
A technical subcontractor is judged on three things: does it state the cost and the delivery date before starting, does it check its work before sending it, does it answer when things get stuck. Here is how we answer all three.
Between the discovery call and the first project put into production.
To receive the itemised quote for a case: lines taken, options, total and date.
The maximum time to answer you on the shared channel, in business hours.
What the first project costs. A real job, produced and delivered under your brand.
It is vagueness: nobody wrote down who does what, by when, at what price. Here are the six situations that really hurt an agency, and the rule we apply to each.
The supplier slips a week, you slip your client by two, and you lose control of your schedule. Here the date is set before we start, and if it moves you are told before the deadline, never after.
Delivered Friday, broken Monday, and you are the one who gets the call. Nothing ships without going through the same checklist every time: browsers, mobile, forms, redirects, performance.
The quote said one figure, the invoice shows another. The price quoted is the price paid. Any out-of-scope request is priced and accepted in writing before it is carried out, or it is not carried out.
The day you change supplier, nobody understands what was done. You get a clean Git repository, explicit names, and a handover note written for someone who has never seen the project.
The quality delivered is not the quality you sold. You approve every deliverable before it reaches your client. Nothing gets to them without passing through your hands first.
Three days of silence while your client waits. One channel, one named contact on each side, a reply within 4 business hours. Planned time off is announced in advance.
The first four steps happen only once, and fit inside 48 hours from the call. Each produces a written document, so you know where the work stands without having to ask.
Many agencies will say nothing about their client before an agreement is signed. That is fair. Ask for it and it goes out the same day, with no conditions and without committing you to anything. If your agency has its own, we sign yours.
We look at what your agency does, which disciplines you are saturated on, and how many projects a month you would hand over. If the need falls outside our scope, we say so there, not three weeks later.
Confidentiality, non-solicitation of your clients, transfer of rights, rate card: a single one-page agreement covering every project that follows. Straight after, a named contact on each side and one channel through which everything passes.
You send a real job, not an exercise. We produce it in full and deliver it under your brand, with no invoice and no commitment, once per agency. Never more than 48 hours pass between the discovery call and the start of that project.
You open a ticket, you get the itemised quote and a date within 4 business hours. As many projects as needed move forward at once, each with its own date. Every deliverable goes through the quality check, then comes to you, never straight to your client.
What was delivered, how long it took, and where the stated turnarounds parted company with reality. What got stuck, on your side as much as ours: both are said, otherwise the review is pointless. Then we adjust the following month’s volume.
Four commitments you can hold us to, not four sales arguments.
The same checklist applies to every delivery, whatever the discipline: rendering across browsers and on mobile, forms, redirects, performance, basic accessibility.
Access to your environments is named, stored in an encrypted manager, and revoked when the job ends. No shared access, no plaintext passwords.
NDA signed before any detailed exchange, on request and with no conditions. Your end clients are never named outside the file that concerns them.
Full transfer of rights on final payment. You get the Git repository, the source files, and a handover note written for a developer seeing the project for the first time.
Better said upfront than discovered mid-job.
On turnaround, approval, and what happens when things do not go to plan.
contact@kuroflow.comAs many as needed. Every project has its own delivery date, set before we start. An agency that signs three clients in the same week leaves with three dates, not with a queue. And if a deadline cannot be met, you are told beforehand, never after.
You are told before the deadline. And if the delay is our fault, the job is discounted by 10% for each period of delay started. That is written into our terms, not just displayed here.
It is sent to you, never to your client. You get an acceptance note listing what was checked. You approve, or you ask for changes: those within the stated scope are included and not invoiced.
No. Send what you have, even partial. If anything is missing to settle the scope, we ask in our reply. What blocks a job is never a short brief, it is a need whose limits nobody has set.
It is announced in advance on the shared channel, with the dates and what stays covered anyway. Nothing is started if we know the deadline falls in a period we cannot cover.
The first project is free: one of your real jobs, produced in full, delivered under your brand, with no invoice and no commitment, once per agency. You judge on the work before sending us anything paid.
One of your real jobs, produced in full and delivered under your brand, with no invoice and no commitment. Once per agency. Started within 48 hours of the call, and yours even if you take it no further.