Reflection Cloud for Teams
Your 1:1s can be the most valuable
half hour on the calendar.
Not by meeting more often, and not with a better agenda template. Reflection Cloud works on the two things scheduling software doesn't touch: what your people bring into the room, and how the conversation moves once it starts.
Our job is the conversation itself.
A reflection app your team writes in for a few minutes a day, guided by AI that asks questions instead of giving lectures — so material for the 1:1 builds all week. And a guided live session, Pair Reflection, gives the meeting itself a shape.
Try it on your own account first. Signing up is free, and Pair Reflection — the part you would use in a 1:1 — works on the free plan. Seats for the team start at five (¥650 per seat / month (tax incl.)), whenever you are ready. Already decided? Set up your organization
Cost
¥650 per seat / month (tax incl.). Contracts start at five seats.
Payback
You already pay for 1:1 time. This makes that spend work. See the math
Getting started
Self-serve: create your org, pay by card, invite your team — same day.
A single team can also try it today, with no company contract (team leads, start here)
The logistics of 1:1s are solved. The conversation is the part that's still hard.
In teams that have kept 1:1s going for years — with or without software to manage them — the same scenes come up:
- The recurring 1:1 invite has survived every reorg. The conversation inside it hasn't changed in a year.
- There's an agenda template. What actually fills it, week after week, is a status update.
- “How's everything going?” “Pretty good.” Then the manager fills the silence.
- Notes get taken and saved. Reading them back, it's hard to find a conversation that went below the surface.
Some of these scenes may look familiar. We read them as nobody's failure — not the manager's skill, not the report's attitude, not the software.
Conversations stay shallow when neither side has support — nothing helps the report arrive with something to say, and nothing helps the manager give the half hour a shape.
What a 1:1 becomes is decided by two things: what the report brings, and how the manager runs it.
A 1:1 where the report walks in with something on their mind goes deep almost on its own. One that starts from a blank page tends to end as a status update. And the same report, telling the same story, will go deeper or shallower depending on how the manager listens and where they steer. Both patterns are familiar in most workplaces.
Which means the depth of a 1:1 is never a one-variable problem. It depends on the material the report brings and on how the manager runs the conversation — neither side can carry it alone. And it isn't a question of talent or effort, either. A reflection habit rarely sticks without a structure to hold it, and running a good half hour of conversation has mostly been left to each manager's personal craft. Both sides have been working without support. If the responsibility sits on both sides, the support should too. So Reflection Cloud gives the report a daily habit that builds material, and gives the manager a guided way to run the session.
Most 1:1 and performance software is built for a different job — scheduling, agendas, reminders, notes — and it does that job well. Neither of the two supports above is part of it. That's why better logistics never changed what got said.
Your current tools and Reflection Cloud do different jobs
Reflection Cloud's share is the bottom three rows — the ones about the conversation itself.
| The work around a 1:1 | Typical 1:1 / performance tools | Reflection Cloud |
|---|---|---|
Scheduling Setting up and rescheduling the meeting | ||
Agendas & notes Templates, records, shared docs | ||
Reminders Keeping the cadence alive | ||
Material for the conversation A daily reflection habit, so reports arrive with something real to talk about | Daily habit | |
Running the session A prepared flow of questions two people move through together, live | Pair Reflection | |
Safety to be honest Anonymous group reflection builds the experience of saying true things safely — before it has to happen in front of a manager | Daily habit |
If you already run 1:1 or performance software, keep it. Scheduling and records stay where they are; Reflection Cloud takes the bottom three rows — the days between 1:1s, and the half hour itself.
Between 1:1s | Daily habit
A daily reflection habit builds what your people bring to the room
Material accumulates during the week
Each morning and evening, people write for about five minutes — Check-in and Check-out. On days worth digging into, a 15-minute guided Reflection goes deeper. By the time the 1:1 comes around, there's already something to talk about.
The AI asks — it doesn't lecture
Reflection Cloud's AI offers a question first and waits while the person writes, then responds to what they wrote. Prescriptive phrasing — “you should,” “you need to” — is prohibited in the design. The thinking stays with the writer; the AI's job is the angle they wouldn't have found alone.
Honesty gets practiced in a safe place first
In Weekend Reflection Circle, a week of writing is woven into one story, with every participant shown as an anonymous animal. No names, no titles, nothing evaluated — the experience of putting honest words into the world happens first in a place where nothing is at stake.
The half hour changes its job
Reports start arriving with material. The 1:1 stops being thirty minutes of topic-hunting and becomes thirty minutes of going deeper into words that already exist.
The stock of words in step 1 comes from screens like this one — pick how you're feeling, add a line about why. That's the size of it, every morning.
The morning Check-in screen — a re-creation of the real UI, not a screenshot.
The state where people feel safe being honest inside a team is known as psychological safety. Google's study of 180 of its own teams, Project Aristotle, found psychological safety to be the most important of the five factors shared by its effective teams. What Reflection Cloud's anonymous circle builds is the step before that — a person's own experience that honest words were safe to say. It does not guarantee a team's psychological safety.
Inside the 1:1 | Pair Reflection
Pair Reflection gives the session itself a shape
Under the same policy, 1:1 quality still varies by manager — not because of talent, but because running the half hour has been each manager's private craft. Pair Reflection moves that craft into the product: manager and report share one live session and move through a prepared flow of questions together. Because the structure is built in, the manager doesn't need training to run a good session — they get to concentrate on listening. The next section walks through the thirty minutes step by step.
The daily habit builds the material. Pair Reflection shapes the conversation. Making 1:1s work through those two supports is Reflection Cloud's design.
The questions follow ORIMD — Reflection Cloud's extension of the dialogue framework ORID with a fifth stage, Meaning — refined through in-person workshops. Reflection Cloud is built and operated by TIELEC Inc. Company details are on the company and legal information page.
Here's how the thirty minutes actually run.
"Guided" is easy to claim, so here is the actual screen flow. Used for a 1:1, the standard thirty minutes moves through five steps; a second round of questions exists for days when there's a full hour. Everything below is how the product behaves today.
Two people join the same session
The report takes the Player role — answering questions. The manager takes Supporter — choosing questions and holding the space. One of them creates a session and shares the link, and that's the whole setup. From there, both screens show the same thing in real time. Pair it with a video call and it works for remote 1:1s.
The two screens once you're in — the same question and answer on both, in real time. A re-creation of the real UI, not a screenshot.
What this looks like for the manager
No agenda to prepare. The screens carry the sequence from here.
The report picks today's theme
They choose a theme from categories like work and growth, emotions, or personal values, and write a short line about why they chose it.
What this looks like for the manager
The theme and the reason appear on the manager's screen the moment they're chosen. No opening minutes spent hunting for a topic.
The report answers AI-prepared questions (5 of them)
At each step, the AI drafts candidate questions. The manager picks one; the report answers — typing or speaking. The questions move through five angles: Objective, Reflective, Interpretive, Meaning, and Decisional — what happened, how it felt, what it means, and what comes next.
Example questions
"When thinking about your career, what situations or interactions with people leave an impression?"
An Objective question
"Through this reflection, how have your emotions changed?"
A Reflective question
Both are real questions from Reflection Cloud's question set. In a session, the AI drafts candidates on the spot, shaped by the theme and the answers so far.
What this looks like for the manager
Writing the questions is the AI's job; the manager only chooses. Answers appear on the manager's screen and are saved automatically — no note-taking to keep up with, which means the manager can actually listen.
After five questions, the direction flips: feedback time
Now the manager speaks. When this screen opens, the AI drafts feedback questions based on the first half's answers. The two pick one, and the manager shares what they heard and what they honestly think — their own experience included. Notes can be typed or dictated. The time is designed so feedback lands as a gift: offered plainly, never used to steer, with the report free to take it or leave it. Not a handoff of questions — a space where thinking together happens naturally.
What this looks like for the manager
No cold start on “so, here's my feedback.” The AI's drafted questions give the two of you a place to begin.
With a full hour
On days with a full hour, a second round goes deeper (5 more)
The standard thirty minutes is filled by the first five questions, the feedback time, and the summary — that flow alone makes a complete session. When there's an hour, the pair can continue into a second round before the summary. Same format; the AI drafts questions informed by everything answered so far.
What this looks like for the manager
The pair chooses the path. After feedback, a button appears to continue straight to the summary — take it to close out the thirty-minute session, or keep going into the second round.
The AI writes the summary — and questions to keep talking
From everything the two covered, the AI generates a written summary, and attaches three questions meant for the pair to talk through in the time that's left. The session doesn't end at the summary — it opens into conversation. The record lands in both people's histories, ready to revisit before the next one.
What this looks like for the manager
Nothing to write up afterward. The generated questions carry the remaining minutes, and the next session can start from last time's record.
The flow is the same for every pair. That's what makes session quality independent of individual technique — the shape is built into the screens.
Run it enough times and something else happens: the way good questions get chosen and asked starts rubbing off on the manager.
In the app, a session is described as 30–60 minutes: the five standard steps fill thirty; rounds that continue into the second half take about an hour.
1:1s are a means. The goal is people who can think for themselves at work.
Everything so far has been about making the 1:1 work. But neither the 1:1 nor any tool is the point. The point is a state: each person on the team thinking clearly, noticing what matters, and acting on it. Productivity follows from that state — it isn't a target you can aim at directly.
You can see the state in small daily moves. Someone checks how a message will land before sending it. Someone flags a risk while fixing it is still cheap. Someone catches an opportunity and carries it past the idea stage. The capacity underneath all three has a name: metacognition — the ability to look at your own thinking and feeling from one level up.
As metacognition grows, people start moving differently
Considerate by default
Before speaking or acting, they check how it will land on the other person. Working relationships hold up, and collaboration carries less friction.
Ahead of risks
Mid-task, they step back and ask where the current approach leads. Problems get caught while they're still small and cheap.
Sees things through
When an opportunity shows up, they can tell what's missing and what to do next — so it doesn't die as a nice idea.
Stacked up across a team, these three behaviors are what rising productivity actually looks like.
And this capacity is trainable — by repeated reflection
Metacognition isn't a personality trait. It grows through a specific repetition: putting your thoughts and feelings into words, then reading them back from a distance. Reflection Cloud's daily habit is that repetition, shaped into five minutes.
Related research
There's a field experiment on exactly this. In a Harvard Business School working paper (Di Stefano, Gino, Pisano & Staats, 2014), new hires in a company's call-center training program spent the last fifteen minutes of the day writing about what they'd learned. On the final training test, the reflection group scored an average of 22.8% higher than the group that didn't reflect.
The number measures the effect of written reflection after work in that study. It is not proof of Reflection Cloud's results.
So what Reflection Cloud sells an organization isn't 1:1 improvement as such. It's a system in which metacognition — a basic capability — accumulates in each person. The 1:1 is where that change becomes visible first.
Which makes the cost a different kind of line item: not spend on a 1:1 tool, but investment in a basic capability of the organization.
Investments need a payback story. Short term, the hours already going into 1:1s start earning their keep. Long term, the capability compounds and stays. The short-term math is next.
This isn't a new investment. It's recovery on one you're already making.
Run 1:1s across a company and every manager's calendar carries the cost. "We put real hours into this" is a common feeling in those organizations — and the math agrees with the feeling. On top of any software, there's the payroll cost of the meeting time itself. The table below sizes it.
A worked example: the cost of 1:1 time
The assumptions are deliberate placeholders. Swap in your own headcount and rates and the math recalculates.
- Managers
- 20
- Reports per manager
- 5 (100 pairs)
- Cadence & length
- Every other week, 30 min
- Fully loaded cost
- $60 / hour
Assumptions (example)
- Hours per cycle
- 100 pairs × 30 min × 2 people = 100 hours
- Hours per month
- × 2 cycles = 200 hours
- Payroll per month
- 200 hours × $60 = $12,000
- Per year
- ≈ $144,000 + software
Calculation
Conservative on purpose: many teams meet weekly, not biweekly, and prep or note-writing time isn't counted. Either would make the number larger.
As long as the conversations stay shallow, those hours aren't yet buying the dialogue they pay for. Read the other way: there's room to grow the return here without growing the investment.
Reflection Cloud costs ¥650 per seat / month (tax incl.). It's the add-on that makes the investment above do its job.
For the same 100 people as the example, that's ¥65,000 a month — roughly ¥780,000 a year, set against about $144,000 a year of meeting time.
There's also a cost that isn't money: employees' time. Five minutes morning and evening is ten minutes a day of new writing. Those words, though, become the material for the 1:1 and double as prep for goal reviews and career conversations — and the half hour stops being spent hunting for a topic. The design changes where dialogue time goes more than it adds time.
Next to training and coaching, the difference is the shape: a habit everyone keeps
Manager training
One-off, priced per event
Often lands well in the room. Back in the everyday, the effect tends to fade — and keeping it alive isn't part of the format.
One-on-one coaching
High cost per person
Deep where it's applied. Scaling it across an organization multiplies the price quickly.
Reflection Cloud
A daily habit for everyone
Built into each person's ordinary day and priced per seat — so the same setup works for a five-person team or a whole company.
¥650 per seat / month (tax incl.). That's the whole price.
Five-seat minimum, month to month. For 100 people: ¥65,000 a month. Add seats any time; cancel any time, effective at the end of the billing period. For volume beyond 50 seats, ask us for individual terms.
USD pricing applies to customers in the United States; elsewhere, billing is in Japanese yen (¥650 per seat, tax included). Your billing currency is confirmed at checkout. The ¥550 plan mentioned under "team leads" below is the personal Premium plan — a separate plan from the per-seat license.
Create an account, create your organization in the admin console, pay by card — and you can be inviting your team the same day. Invoices and receipts are available in the console for every charge. Contract terms are Article 24 of the Terms of Service.
The same habit supports mental well-being.
Reflection Cloud is not a mental-health product. It's a reflection app. But writing down how you're actually doing, morning and evening, is self-care in its most practical form: noticing stress early, in your own words. "Something feels heavy" becoming "it's that account I'm worried about" is already the first step of coping.
Related research
The effects of writing about emotions and experiences have been studied since the 1980s as "expressive writing" (Pennebaker, 1986–). A meta-analysis of studies with healthy participants (Smyth, 1998) reported improvements in psychological well-being and health outcomes for those who wrote.
These studies measure the effect of writing itself — they are not proof of Reflection Cloud's outcomes. Reflection Cloud is not intended to diagnose or treat any mental-health condition.
The scale of the problem is why this belongs in a business conversation:
Working days lost to depression and anxiety, per year
~12 billion
Lost productivity, per year worldwide
~US$1 trillion
Source: World Health Organization, "Mental health at work" fact sheet (2024).
One design choice matters here. Personal entries are never shared with the employer — not with managers, not with HR (see the three-tier disclosure design). Words written for an audience drift toward performance. Because no one else reads them, people write what's actually true — which is exactly what makes the habit work as self-care.
Where to start depends on your seat.
Three common starting points.
Team leads & managers
Your team can start today — no company contract required.
Each member signs up for a personal account — no procurement, no approval chain (if your company has policies about new tools, a quick check with IT is worth it). Signing up is free, and Pair Reflection is available on the free plan; the free plan limits access to past history and to AI feedback. The full experience is the personal Premium plan — $5.99 a month per person in the US, ¥550 elsewhere — paid individually. Daily entries are visible to no one else, including you; what a session shares with the other person is that session's answers, nothing more. If it earns its place, company-wide rollout is a later conversation.
Three steps, starting today
- 1.Members sign up free from the home page
- 2.Open a Pair Reflection session and share the link
- 3.Run your next 1:1 inside that flow — thirty minutes
People & HR leaders
Start with the data question — it's usually the deciding one.
What the company can and cannot see is designed as three explicit tiers, and the boundary is written into the Terms of Service as a contract condition — not a policy page. How the product produces its effect (reflection as training for metacognition) is laid out on this page too. Both are a scroll away.
Founders & budget owners
Start from the money. Most of it is already being spent.
An organization running 1:1s is already paying for them in salaried time — in the worked example on this page, about $144,000 a year for a 100-person setup, before any software. Reflection Cloud is $6.99 per seat a month: a line item that exists to make the hours already being paid for produce dialogue.
If you are a coach, therapist, counselor, career coach, or facilitator using Reflection Cloud in your own client work, see the page written for practitioners.
What your organization gets: three features.
All three are live in the product today. Anything on this page that isn't built yet says "planned" right where it's mentioned.
01
Between 1:1s | Daily habit
A personal reflection practice
Morning and evening Check-in / Check-out, about five minutes each, plus a 15-minute guided Reflection for days worth going deeper. Dream Support (setting goals and revisiting them) and Life Navi (mapping your career and values) live in the same app — so the habit also feeds goal reviews and career conversations, not just 1:1s.
02
Between 1:1s | Daily habit
Weekend Reflection Circle
On Friday night, the week's words are woven — anonymously — into one story, delivered for the weekend. Participants appear as animals; no names, no titles. It's the experience of being honest out loud, with the stakes removed. Unique to Reflection Cloud.
03
Inside the 1:1 | Pair Reflection
Pair Reflection
A live shared session where two people move through a prepared flow of questions together. Run your 1:1s in this format as-is — the thirty minutes is exactly as shown above.
The Enterprise plan bundles all three. Every member gets unlimited AI use, and seats are managed from a single admin console — assign, unassign, and reassign as people come and go.
Individual records are never disclosed to the employer. That's what keeps the data honest.
"What can the company see?" is the first question in almost every conversation about workplace reflection tools — and often the deciding one. Our answer isn't a reassurance that privacy matters to us. It's the design itself: exactly which information reaches the employer, laid out in three tiers.
Surveys filled out under one's own name tend to read the same way everywhere: polished, safe, careful. Words written with an audience in mind drift toward performance. Reflection Cloud's entries are honest for a structural reason — they're written somewhere no one else can read. And statistics built from honest words reflect reality better than statistics built from performed ones. Keeping individual records sealed isn't a legal disclaimer. It's the quality condition for the data we hand you.
What the employer sees, in three tiers
| Tier | To the employer | What it is, and how it's designed |
|---|---|---|
| Individual records | Never disclosed | The reflections themselves. Row-level security (RLS) in the database means each person's records are readable from their own account only — there is no access path for anyone else, employer admins included. This is implemented fact, not policy. |
| Statistics | Disclosed | Usage and continuation rates, participation by department — numbers with no individuals in them, designed with k-anonymity: figures for groups below a minimum size are never shown, so small teams can't be reverse-read. This tier is planned, not yet built; this scope and this design are what we intend to provide. |
| Climate | Disclosed | A report in which AI reads anonymized, aggregated words and describes organization-level tendencies only — no line traceable to a person. Also planned, not yet built, under the same rule: this scope, this design, and nothing more specific promised in advance. |
For the two planned tiers, we don't promise dashboards or specific screens in advance; when they ship, they'll begin as reports, scoped exactly as described. And the same three-tier map is shown to employees. Knowing the company sees only the two aggregate tiers is what makes writing honestly a rational thing to do.
What IT and security teams usually ask
| Item | How Reflection Cloud is built |
|---|---|
| Access to individual records | Reflections and entries are protected by database row-level security (RLS): readable from the writer's own account only, exactly as the “Individual records” tier above describes. |
| Employer-facing viewing or reporting | No feature shows an employer individual entries, and none will be built. What organizations receive is limited to the statistics and climate tiers above — both designed so that no individual can be identified. |
| Anonymity between coworkers | Weekend Reflection Circle participants appear as anonymous animals, and the woven story doesn't identify anyone. |
| Data sent to AI | AI processes entries only as needed to generate questions and feedback. Processing uses external AI providers' APIs under contract terms in which submitted data is not used to train their models. |
| Encryption in transit | All traffic between the app and our servers is encrypted with TLS. |
| Devices & deployment | Nothing to install. It runs in the browser on phones and computers; no device rollout or network changes are needed in the usual case. |
For anything not covered here, ask through the contact form. We answer plainly — including about what doesn't exist yet.
None of this rests on this page alone. Article 24 of the Terms of Service — the article that governs corporate contracts — makes it contractual: the employer cannot view members' records or per-individual usage, and cannot request their disclosure or deletion. What an organization sees is limited to members' names, email addresses, seat assignments, and invitation status. The clause keeps applying after an employee leaves, and after the contract ends.
What Reflection Cloud gives an employer is a reflection habit employees keep for themselves — and organizational data that never points at a person.
Getting started
Self-serve, end to end. And however you start, start small — one team, a handful of seats — and widen only if it earns it.
Contract in the appsame day
Create an account and your organization
Sign up free, then create your organization from the admin console. All it needs is a name.
Pay by card
Confirm a billing email and subscribe from five seats up. Invoices and receipts are available in the console for every charge.
Invite and assign
Invite members by email; assign seats as they join. That's day one.
¥650 per seat / month (tax incl.), five-seat minimum. Contracts above 50 seats and bank-transfer invoicing are handled individually — use the contact form below.
Prefer to ask something first?
Write to us through the contact form — where you are in the process, what you'd want out of it, and whatever question is in the way. We'll answer in writing, honestly, about what the product does and doesn't do today. A question is just a question; it doesn't sign you up for a sales cadence.
Frequently asked questions
Toward 1:1s your people walk into with something to say.
Run it once yourself, then decide. Start with one team and a handful of seats. If the conversations change, you'll know.
¥650 per seat / month (tax incl.) · five-seat minimum · cancel anytime, effective at the end of the billing period
Already decided? Set up your organization. Questions get answered in writing, plainly.