Urume Maruboshi

Peer Loop🥬
Not approval. Not signature. Just circulation.

[Urume Maruboshi @kailan_peerloop]

How Kailan works.

1. Upload a doc
2. Share a link
3. Your team taps Agree, Pass, or Question
4. PDF proof — done ✨

That's the whole thing. Free at https://t.co/x4TyV5fuwz 🥬

#SaaS #productivity #documentreview #teamwork #remotework #PeerLoop #FreeTools

[Urume Maruboshi @kailan_peerloop]

"Didn't we already agree on this?"

If you've heard this in a meeting, you have a documentation problem — not a memory problem.

Simple ways to keep a record that sticks 👇
https://t.co/xdeYJc3wi5

#teamwork #productivity #documentation #projectmanagement

[Urume Maruboshi @kailan_peerloop]

You're not the manager.
But you need the team aligned.

A 3-step framework for building consensus — no title required 👇
https://t.co/gSyJ9mUpKz

#leadership #consensus #teamwork #careeradvice

[Urume Maruboshi @kailan_peerloop]

"Should I send a reminder…or will I look pushy?"

Every team member has had this thought.

Here's how to follow up without the awkwardness 👇
https://t.co/QgUDMTdAYV

#workplace #communication #teamwork #worktips

[Urume Maruboshi @kailan_peerloop]

5 people × 30 min meeting = 2.5 hours of team time.

For a decision everyone already agreed on.

4 ways to get team agreement without scheduling another meeting 👇
https://t.co/mFYyQO2kZG

#async #productivity #teamwork #meetings

[Urume Maruboshi @kailan_peerloop]

You shared an update.
No one confirmed they read it.
Monday comes — "Oh, I didn't see that."

Sound familiar? Here's how to fix it 👇
https://t.co/vS4gLSmuXb

#teamwork #productivity #remotework #communication

[Urume Maruboshi @kailan_peerloop]

We didn't build an approval tool.
We didn't build a signature tool.

We built a way for peers to touch a document and leave a mark.

[Urume Maruboshi @kailan_peerloop]

Share a Kailan three ways:

→ Open link (anyone can respond)
→ Password-protected (controlled access)
→ Direct invite (Google account required)

Pick what fits. https://t.co/x4TyV5eWH1

[Urume Maruboshi @kailan_peerloop]

Approval chains make sense — until your 3-line update needs sign-off from four people who are all in different time zones.

[Urume Maruboshi @kailan_peerloop]

Approval = vertical.
Circulation = horizontal.

Kailan doesn't ask "who's in charge?"
It asks "who's in the loop?"

[Urume Maruboshi @kailan_peerloop]

Every Kailan ends with a PDF.

Who responded. When. What they chose.

No screenshots. No "I think they said yes in Slack somewhere."

https://t.co/x4TyV5eWH1

[Urume Maruboshi @kailan_peerloop]

"Can everyone confirm they've read this?"

*silence*

One follow-up email. Then another. Then a Slack message. Then you give up.

[Urume Maruboshi @kailan_peerloop]

Not every decision needs to go up.
Some just need to go around.

That's Peer Loop.

[Urume Maruboshi @kailan_peerloop]

Kailan in 30 seconds:

1. Upload a doc
2. Share a link
3. Your team responds: Agree, Pass, or Question

That's it. PDF proof generated automatically.

https://t.co/x4TyV5eWH1

[Urume Maruboshi @kailan_peerloop]

You sent a doc for review.
Three days later: "Sorry, haven't looked at it yet."

There has to be a better way.