Fixed project or ongoing partnership

Choose a fixed project when you are buying a launch with an edge. Choose an ongoing partnership when the product keeps changing and you want the same people in the work. The choice of design retainer vs project is a question about the shape of the job. It is a question of what "done" means, and of whether the same people should still be in the files after launch.

Both shapes can be honest. Both can waste money when they are used for the other job. The decision gets clearer when you name what "done" means.

A fixed project has an edge

A fixed project ends. The edge might be a marketing site, a brand system small enough for the team to use, a store migration, or a first version of a product interface. The scope names the pages, the states, and the handoff. When those exist, the project is finished, even if the company is not.

This shape fits a founder who can describe the offer well enough to brief it. The date matters because something else is waiting: a raise, a season, a shutdown of the old site. You want design and production code from the same small team, then you want the repository, the domain, and the content logins in your name.

Hanabi's public work sits mostly in this shape. Down the Cove was an ecommerce restructure, migration, and redesign with a store that had to come out the other side. Thomas Bewick needed an editorial site that still felt like the craft. A fixed edge is what made those definable. The work had a before and an after.

A fixed project includes a way to change your mind, in writing. Priorities sharpen. A page drops, a page enters, the date is said out loud. What it should not include is an unmarked second project hiding inside "quick tweaks" after the edge has been crossed.

An ongoing partnership has a continuing job

An ongoing partnership fits when the interface, the site, or the brand system will keep changing after the launch, and you want the people who already know the files. A product that ships weekly, a catalog that gains a new line every month, a marketing site that must track a moving offer: these are continuing jobs.

The retainer, if you use that word, is a reserved capacity and a standing context. The same people stay. They already know why the type works, where the headline lives in the code, and which sentence the company refuses to say. You are paying so that knowledge does not reset every time a screen needs a change.

Google's guidance on helpful content is a useful boundary for what that continuing work should be. Search Central says ranking systems aim to reward content made for people, and it treats a pile of pages produced in the hope that some of them rank as a warning sign. An ongoing partner who fills the calendar with undifferentiated posts is manufacturing motion. A useful month improves the pages buyers already need, fixes the sentence people misunderstand, and ships the next real surface of the product.

What changes between the two

The brief changes. A fixed project can be scoped from pages and states. An ongoing partnership needs a priority each cycle, because the full future cannot be listed. You still write down the cycle's work. "Ongoing" is a poor excuse for a month with no decided outcome.

The review cadence changes. A fixed project can live on a weekly review until launch. A partnership needs a smaller, steady rhythm so decisions do not pile up into a fake relaunch every quarter. The channel stays the same either way: one place, written decisions, honest dates.

The handoff changes. A fixed project should end with the repository, a content map, and a place the brand files live. Hanabi's client portal is that place for assets, docs, and updates. A partnership still owes you that ownership on day one. Continuing help is an invitation, not a lock on the accounts.

The feeling of urgency changes. A fixed date concentrates attention. A partnership can go quiet and still be valuable, as long as the quiet months are a choice. If every month feels like an emergency, the scope is a fixed project that was never given an edge.

How to tell which you need

Ask what would count as finished in the next few months.

If you can point at a site, a brand kit, or a product slice and say "when this is live, we stop," you want a fixed project. Leave room for a follow-on. Do not pre-buy a year of unspecified hours to feel safe.

If the honest answer is "we will still be changing the core flow in six months, and we want the same judgment in the room," you want an ongoing partnership. Define the first cycle anyway. The first cycle is how you learn whether the working relationship is real.

A common middle path is honest: a fixed project for the launch, then a short partnership once you have seen the team build. Reversing that order is harder. A retainer with no launched edge becomes a long conversation.

The other hiring choice sits beside this one. A freelancer, an in-house designer, and a studio solve different problems. Studio, freelancer, or in-house for a first serious site is the next piece if you are still deciding who should hold the work, before you decide how long they hold it.

What neither shape should hide

Neither shape should hide who does the work. Ask whether the people on the call are the people in the files. A fixed project staffed by a rotating bench, and a retainer that is only a ticket queue, fail the same test.

Neither shape should hide ownership. You own the repository, the domain, the analytics, and the content accounts in both cases. A discount that depends on the studio keeping those is a dependency with a nicer name.

Neither shape should hide the communication standard. Clear updates, honest timelines, and fewer surprises apply to a fixed launch and to a monthly partnership. The partnership version is stricter, because a vague month is easy to repeat.

If you know which shape you are buying and want to test it against a real offer, book an intro call with Hanabi. The call should end with fit and a rough shape of the work, including whether the work has an edge or a continuing job.