Shared bench · not the client site

Prairie Sailor Branding

The record from the October 14, 2026 call. Anthony shapes the work in Base44. Justin ports it, tests it, and keeps it somewhere we both can change. This page is that somewhere. It is not Base44, and it is not pscbranding.com.

Anthony is finishing the prototype Justin is waiting on that handoff October 14, 2026

Next move. Anthony sends the working Base44 build, plus links to the client sites that already exist. Justin does not keep polishing the front until that arrives.

Where it stands

Four things are in motion. Only the first one is Anthony's to finish before the build starts.

1
Anthony finishes Base44
2
He sends it, with client-site examples
3
Justin ports it off Base44
4
We test it, then the team does
Anthony Now

Finish the prototype

Images, the job and purchase-order workflow, and a first pass at the customer side. When it feels right, send it. Also send the existing client sites, even if they are rough. They show how ordering works today.

Justin Waiting

Do not spend more front-end time yet

A public-page pass already exists on Justin's machine from earlier on October 14. It is not the product. The next front-end work starts when Anthony says the Base44 version is the one to port.

Both This page

Talk here, not inside his builder

Decisions, the handoff, and the test list live on this bench. Base44 stays Anthony's sketchbook until the handoff.

What we are building

One company site. Three doors. Prairie Sailor the goods brand and Prairie Sailor Branding stay separate. The clothing photos on the earlier demo were stand-ins.

Public

A short front door

Big, direct, Kansas City, and how the work gets done. People often arrive from a one-sheet and already know you. Dylan's short film can live here when it is ready. Little logic.

Staff

Jobs, orders, history

Active jobs, purchase orders, a cork-board overview, and a record of what changed: price, artwork, approval. Anthony sees every job. Frank sees the jobs he opened. A sales role can do less than an admin.

Client

Where the order is

A status the client can read: art, approval, in the works, on the way. Internal notes never show up there. Updating the job is what moves the client's status.

Staff reach it from the branding site, Staff access, on a phone. It is a website with a home-screen shortcut. It does not go through the App Store. One site, not two products.

How a client spends

Anthony named three ways money moves. The first version uses two. The third waits until a client pays to have it.

First

Invoice the company

People order inside a limit. The company gets the invoice. CapFed was the picture: many locations, one company pays.

Second

Credits on the account

The company loads an amount. People spend it. Going over asks the person who can approve more. Reloading should be obvious before the balance hits zero.

Later

A person's own card

St. Luke's was the odd case, a department or a person buying a few shirts. That is a switch we can add, or its own portal. It is not the frame we build first.

New companies start from one build. Branding changes. Features turn on or off. We do not design a different product for each client. A public shop is not the door: email domain or store number has to match, because open links have pulled in orders from people who were not the client.

Email the model

The part the call summary skipped. The staff site holds the jobs. The daily push, and the reply, happen in email so nobody has to live in a chat window.

  1. A morning note for the people who need one. It walks the open jobs and says what changed yesterday, what is hot today, and what can wait. Justin's own bots send his at 6:55am. The clock for Prairie Sailor Branding is not set yet.
  2. The note is a short list, numbered. A reply can say: do 1 through 5, tell me more about 6, do not do 7. That reply is the instruction. It should read like a note to an employee.
  3. The reply comes back with proof. What got done, a link or a screenshot, and anything that still needs a yes. Checking it fits on a phone.
  4. Frank can update a job in a sentence. "Artwork approved by the customer" becomes a line on that job. He does not retype the record, and he does not see jobs he did not open.
  5. The client sees status, not the note. The same update can move their tracker. The sentence Frank typed, and anything internal, stays on the staff side.
  6. Ads and social posts are a later switch. Google and Meta reports can show on the client side and go out on a schedule. A pack of ready social posts can be a paid add-on. Neither one is this first build. The merch desk can sit with Frank while the advertising work stays the main business.

What "done" means for this idea. Anthony can read one email, answer it, and see the job change without opening a builder. Frank can do the same for his own jobs. A client can open their status and not find an internal note.

When the prototype is ready

  1. Anthony sends the Base44 build and the old client-site links.
  2. Justin prices the port before the long build, from that real prototype, not from a guess.
  3. The code leaves Base44. It goes into GitHub, with a database and a host Justin can change. Base44 can keep the sketch. It should not be the system of record. Logins have to be usernames and passwords the team can hand to Frank. The builder would not do that.
  4. Justin tests the paths. A full job for a sample customer. Sales view against Anthony's view. Permissions. An order that should update the client, and a note that should not.
  5. Anthony and the team try those same paths and say what is wrong.
  6. Then it can sit on the branding site as Staff access. Shopify stays available. Whether the live shop stays the front counter is a later choice, not a reason to stay inside the builder.

Still open

Scope

Another working session after the prototype

The customer door, the exact sales permissions, and which switches ship first. Anthony does not have to finish a perfect customer site. A clear pass is enough to price.

Money

No fee is locked

See the working arrangement below. Anthony is thinking about it. Justin will price the port when the prototype arrives.

Stack

GitHub, a database, a host

Named on the call as the direction. The specific database and host get picked at the port, not before.

Examples

Named so the rules are concrete

CapFed, Commercial Electric Supply, and St. Luke's came up as pictures of how orders work. They are not a promise that those builds are sold. A couple of HVAC conversations and a car-parts company were mentioned the same way.

How we work together

Said on the call. Not signed. Anthony asked for time to think about the split.

Shape

Project, then hours

A first build for a price, then hours when something actually needs doing. Some months that is a few hours. Some months it is none.

Monthly

A slice while the doors are open

Tied to clients living on the system. New features, like the social-post pack, are extra. The monthly amount is the maintenance. The new ductwork is a separate job.

Role

On when you need him

Justin does not take a book of forty clients. Anthony turns him on. During a project that can be an email once or twice a week. Justin is the only person Anthony has to talk to.

Justin named $50 to $100 an hour as the range he wants, and offered to discount the first build in exchange for that monthly slice. He described a past build of about 40 hours that he would bill closer to 15 or 20 hours at $100. The exploratory pages already made for this meeting are not a bill. Anthony said he is open if it makes sense for both, and that he likes project work plus hours after, with a monthly amount on top.

Once a month the group can sit down, trade what they are seeing, and bring each other into the right rooms. There is a desk at the office when Justin wants it. Frank's larger asks come through Anthony until this system is actually in use.