Keep-fresh · Changes

Hours changed. Say so.

Saturday at the bakery. Winter hours at the clinic. Emergency out of office. A celebration. A note to customers. A line that helps the next neighbor call. The door and the phone and the site should say the same thing.

This week

You send the words. I put them up. Evening batch. A few days. Nothing live until you say yes.

Bakery chalkboard hours on the sidewalk at dawn. — Saturday hours. On the board and on the site.

Clinic glass door with winter hours matching a phone. — The door and the phone say the same thing.

In

Hours and holiday hours.
Emergency closed / out of office.
A hire, a service renamed.
A celebration the door already knows.
A customer note.
A workflow sentence that gets the next call.

Not

A new booking flow.
A new information architecture.
A rebuild of how the shop works online. That needs a scope first — a Feature add, or a project. We’ll quote it.

What this is. What this is not.

Done means we wrote it down.

Keep-fresh is what already exists in the shop. A project starts when we write what “done” means.

Keep-fresh

You send it. I put it up.

Photos, reviews you already have, hours, hires, specials, OOO, a celebration, a note to customers, a color pass. Hosting and SSL stay up. Evening batch. A few days. Nothing live until you say yes. In year one. Then $449/yr.

Feature add

A new thing on the public site — or bigger.

A page, a form, a gallery, a booking block. A managed CRM if that’s the work. Dreaming is allowed. Building starts after a written scope: what ships, what does not, what “done” means. Price after we know. If it cannot be named in one sitting, it stays an idea.

A project

Separate quote.

Rebuild. Redesign. New architecture. Member/app, mail server, general IT. A pile of keep-fresh asks that is actually a new section. Done means the scope shipped — not “keep going until it feels finished.”

Nothing goes live until you say yes. Included in year one. Then $449/yr.

Write Packages The idea