Themes updated: protected time to learn the AI tooling is rising.
The Route · Live
One shared truth, drawn as the climb it actually is.
Every voice memo, email, and meeting flows in. The hub distills it onto this map. Both teams look at the same mountain.
Drag the map to explore the route
1 / 7
Waypoints underway
Current position
Kickoff
Goals captured, map is live
Next waypoint
Basecamp: Land
Eng session with Matt + Alan
Planned descents
1 pass
Security + SDLC, on the route by design
Summit window
Months 6-12
Customer-facing at scale
02 · Distilled feed
Everything that happened, minus the noise.
Raw input arrives as calls, emails, docs, and portal events. The hub publishes only the distilled record: what was decided, who carries what, and any signal worth knowing.
Meeting captured: Molly + Joe intro (32 min)
Decisions
- First working session with the engineering team to be scheduled
- Engineering intro session with Matt + Alan to be scheduled
- First deliverable: a live build-walkthrough session
Next steps
- Molly: schedule the session, share a systems overview
- Joe: session prep, recap note
Signals
- Pilot walkthrough well received
Auto-distilled by the hub · open the raw transcript any time
Voice note posted, distilled into two next steps and one risk.
Shared: engagement roadmap draft v1.
Kickoff goals confirmed by both teams.
03 · The Composer
Talk to the hub.
Voice memos, emails, meeting notes, quick updates: post anything in your own words. The hub distills it into next steps, decisions, and risks on the shared record.
Try:
What you say
Private to you
Read-only team view. Posting stays with your own account.
Raw input visible only to you. Published record visible to both teams.
What the hub publishes
Visible to both teams
Nothing posted yet. The published record appears here.
04 · Balls in play
Who carries what, in the open.
A two-sided tracker of every open item on the route. No private task lists, no status-chasing emails.
Radical transparency: both sides see the identical list. When something moves, the hub surfaces it. Nobody chases anybody.
Ameris carries
3 open
Share the systems overview
Current architecture and tooling context, ahead of the working session
Schedule the engineering session
Working session with Matt + Alan, live build walkthrough
Pick the first two build targets
From the joint tooling audit; the hub surfaces options
LunarCrush carries
2 open · 1 done
Build-walkthrough session prep
Pilot-site rebuild, prompts, folder and context system
Recap note
Distilled recap of the Molly + Joe intro call
Roadmap v1
Shared to the engagement, Jul 16
05 · Team
Your email domain is your team.
Sign in with LunarCrush, land on your company’s side of the table, done. No invites, no admin console, no user management: everyone at amerisbank.com is Ameris, automatically.
Ameris Bank
· amerisbank.com
6 members
MW
Sponsor
Molly Walker
via LunarCrush OAuth
M
SVP Engineering
Matt
via LunarCrush OAuth
AC
Mortgage Technology
Alan Cooper
via LunarCrush OAuth
G
Team
Gino
via LunarCrush OAuth
R
Team
Ross
via LunarCrush OAuth
DR
New
Enterprise Architecture
Dana Reyes
joined today · via LunarCrush OAuth
LunarCrush
· lunarcrush.com
1 member
JV
Lead
Joe Vezzani
via LunarCrush OAuth
Tenant isolation
Ameris sees Ameris. Nothing else.
Your domain unlocks exactly your engagements. There is no global view to fall out of, and no setting to get wrong.
What this team sees
- Their map: the route, camps, and progress
- Their feed: every distilled call, email, and doc
- Their decisions: the append-only log
- Their files: everything shared into the engagement
What this team can never see
- Other client engagements
- LunarCrush internal tools
- Anyone else’s data, anywhere in the hub
Isolation is structural. Scoping is by engagement and enforced at the session, not hidden by the UI.
THE ONE EXCEPTION
JVjoe@lunarcrush.comAdmin
One admin sees every engagement and keeps the map honest. Placement never needs an admin console: domains do the work, and edge cases take one chat with the hub AI. "Move this contractor to the Ameris team", done.
06 · Voices
Every voice on the map.
Every member of both teams gets the same three prompts: what matters most to you, what you would love to see change, and what is blocking you. The hub distills the answers into one shared board, so the quietest person in the room moves the map as much as the loudest.
Your voice
Private to you · published only as themes
Prompts:
Read-only team view. Sharing stays with your own account.
Shared. Themes and counts update as the team posts.
What the team is saying
Distilled from every voice across both teams. Counts and trends update as people share.
- Ideas die in the gap between a whiteboard and a funded project; members want a same-week path from idea to working prototype.
- The pilot walkthrough made the gap visible: what took quarters can take days.
- Members describe waiting months for small changes to vendor tools they use every day.
- Strong appetite to build thin internal tools instead of filing feature requests and hoping.
- Members want learning time on the calendar, not squeezed around sprint work.
- A recurring ask: pair the training with a real backlog item, so the time counts twice.
- Nobody wants a certificate; everyone wants a shipped thing they built themselves.
- Members want a written line between safe-to-automate and needs-review before they start building.
- The goal is confidence, not caution: clear rules make people move faster, not slower.
- People who build internal tools want that work visible in reviews, not treated as invisible glue.
- A suggestion already circulating: demo days where builders show what shipped.
Blockers board
What is in people’s way. Raised means the hub heard it; Routed means it is on someone’s plate; Clearing means the fix is in flight.
Routed
Ameris
surfaced by 3
Sandbox access requires three approvals
Members can’t try the tooling without a multi-step sign-off chain.
Clearing
Joint
surfaced by 2
No test data safe to use
Fix in flight: the synthetic-data lab lands at Camp 1, so nothing real is ever touched.
Raised
Ameris
surfaced by 2
Coding-agent seats not yet enabled
Developers ready to build are waiting on licenses to be switched on.
Routed
Joint
surfaced by 3
Unclear who approves an internal tool going live
The go-live approval path needs one named owner on each side.
07 · Decision log
Every call, on the record.
Decisions are extracted from whatever medium they happened in and pinned here with their source. The log is append-only and visible to everyone.
| Decision | Date | Source |
|---|---|---|
| All tooling stays inside the Copilot / M365 fence | Jul 17 | Meeting |
| Phases 1-2 touch zero customer data | Jul 17 | Roadmap |
| First deliverable: build-walkthrough session | Jul 17 | Meeting |
| Weekly working cadence confirmed | Jul 16 |
Anyone can flag a logged decision for review. The hub reopens it as a discussion item, never as a dispute between people.
08 · Engagement summary
Meridian Capital
Data Partnership · admin summary. The Meridian team sees the full app for this engagement; this is the distilled state at a glance.
Kickoff
Basecamp
Camp 1
Camp 2 · First proof
Summit
Open balls
5
3 Meridian · 2 LunarCrush
Last distilled event
2h ago
Meeting transcript, auto-distilled
Members
9
via domain auto-join
Recent distilled activity
Meeting captured: Priya Shah + Devon Kohl, evaluation-window sync (28 min). Two next steps routed.
Shared: sample panel v2, cleared for the evaluation window by Priya Shah.
08 · Engagement summary
Halcyon Insurance
AI Enablement · admin summary. Kickoff is still being scheduled; the route below is drafted and waiting for the first working session.
Kickoff · scheduling
Basecamp
Camp 1
Camp 2
Summit
Open balls
2
Both on scheduling the kickoff
Last distilled event
3d ago
Email thread, auto-distilled
Members
4
via domain auto-join
Recent distilled activity
Email distilled: Elena Marsh proposed two kickoff dates; scheduling ball routed to Halcyon.
Engagement created: route drafted, waiting on Owen Pratt to confirm the sponsor group.