Most tools treat every new login the same way: welcome screen, setup checklist, “tell us about your business.” That’s a reasonable default for a founder signing up for the first time. It’s actively wrong for the fourth person joining a company that’s been running for two years.
We wanted to know what actually happens the first time someone who isn’t the founder logs into an established Craft11 account. Not what we hoped would happen. What actually renders on screen.
What we built, underneath a fairly quiet feature
Inviting a team member is a real endpoint, not a placeholder: the owner or an admin sends an invite, the system creates a real user under the account with a temporary password to hand over manually, and that person’s role, admin, manager, field rep, viewer, is a genuine structural fact from the moment the account exists. Not a guess Stark makes later. A real field it can read immediately.
Deactivating someone works the same honest way in reverse. Their login gets blocked immediately. Nothing about their history gets touched: every task, every note, every assignment stays exactly where it was, correctly attributed to them, because deleting a departed teammate’s fingerprints from two years of client history would be its own kind of institutional memory loss.
What actually happens on their first login
A newly invited manager logs in for the first time. No setup wizard runs. No “let’s configure your pipeline stages.” Stark’s first message doesn’t treat this like Day One, because structurally, for this company, it isn’t. Instead: real pipeline numbers, what’s actually open right now, who’s assigned to what, a genuine orientation grounded in the company’s current state, not a generic tour of empty menus.
Ask it to see a real offer, the client list, active projects, and each is a real navigation with Stark narrating what’s actually there, not a demo walkthrough of sample data. The context that took the founder months of daily use to build up is just there, on someone else’s first day.
The line that made the point better than we could have written it
During testing, we asked Stark what a brand-new team member would need to know to get oriented. On a mature account, its answer named a real team member by name, cited a real two-day ramp-up time, and closed with a line worth quoting directly, because a human didn’t write it for marketing purposes, the system said it while doing its actual job:
“The Vault is what makes ramp time about two days instead of months.”
Neither the number nor the sentence was written by us. It came from a live model reading real, accumulated company history and describing, accurately, what that history is actually for.
Why this matters more than it sounds like it should
The usual pitch for “institutional memory” software is aimed at the founder: you’ll remember more, forget less, work faster. All true, and also incomplete. The real cost of an undocumented business isn’t just what the founder forgets. It’s what every new hire has to be told, in person, by someone whose time that costs, over and over, company after company, hire after hire.
A new person walking in and getting a real, current, accurate picture of the business without anyone stopping their own work to explain it isn’t a nice-to-have around the edges of the product. It’s the same compounding memory the founder’s own questions get sharper from, just paid out to someone else, on their very first day, instead of locked to whoever happened to build it up.