Three coaching modes. One powerful platform. From quick answers to deep personal growth.
No credit card required • All 3 modes included • Start in 30 seconds
Stop tab-switching between Scrum guides, blog posts, and Stack Overflow. Expert mode quickly understands your context, then delivers precise, actionable guidance tailored to your situation.
"I used to spend 30 minutes researching best practices for refinement meetings. Now I get comprehensive answers in 10 seconds."
— Sarah, Scrum Master
"How do I run sprint planning? We keep running over time."
Before I tailor this for you—what's your team size, and roughly how long are your sprints?
"7 members and we are already in 3rd sprint!"
Great context—three sprints in with a team of seven is exactly when planning starts to feel painful if the structure isn't tight yet. The good news: this is very fixable.
For a two-week sprint with seven people, planning should take no more than two hours. Here's what's likely causing your overruns, and how to fix it.
The most common culprit: starting planning without a ready backlog. If your Product Owner is clarifying stories during planning, you'll blow your timebox every time.
A tight two-hour structure: First 15 minutes for sprint goal. Next 45 minutes for story selection—if any story triggers more than 5 minutes of discussion, park it. Then 50 minutes on task breakdown and estimation. Final 10 minutes: commitment and board setup...
[Continues with immediate wins and next steps]
"Our remote team feels disconnected. People seem disengaged in meetings and collaboration is suffering."
That's a challenge I hear often with distributed teams. Tell me a bit about your setup—how distributed are you, and what does "disengaged" look like? That'll help me share the most relevant patterns.
"Fully remote across 3 time zones. People keep cameras off, don't speak up in standups, and async work feels slow."
That context helps—fully remote with time zone spread creates specific challenges. Here are three documented approaches:
1. Team Topologies (Skelton & Pais) has documented work on remote-first team interactions. Their book and research on teamtopologies.com emphasize explicit communication protocols and defining when teams use synchronous vs. asynchronous collaboration—particularly important for distributed teams.
2. Martin Fowler's blog on remote work patterns documents that distributed teams often benefit from "heartbeat" communication—short, frequent check-ins rather than long scheduled meetings. The pattern creates connection without meeting fatigue.
3. Esther Derby's work on team agreements emphasizes that teams create their own working agreements together. For remote teams, this might mean agreeing on response times, when to use video, and how to handle async work—agreements created by the team, not imposed...
Which of these resonates with what you're seeing? I can point you to specific resources if helpful.
Stand on the shoulders of giants. Mentor mode shares proven patterns from documented Agile practices, published research, and thought leader frameworks—giving you multiple approaches to try, each with full citations so you know where it comes from.
"Instead of being told what to do, I learned *why* these practices work. That understanding changed how I facilitate my entire team."
— Marcus, Product Owner
The toughest problems aren't technical—they're human. Coach mode helps you explore what's really happening, recap to ensure understanding, generate alternatives, and tap into where you have energy to take action. You find the answer—and own the outcome.
"We had a team member who dominated every conversation. Coach mode helped me see my own role in that pattern and find a way forward that honored everyone."
— Jennifer, Agile Coach
"Our retrospectives aren't working. People don't engage."
What specifically are you observing when you say people don't engage?
"They're mostly silent. One-word answers. Our manager sometimes sits in."
Let me make sure I understand. What I'm hearing is: people are silent, giving minimal responses, and your manager's presence might be a factor. The core issue seems to be about feeling safe to speak up. Is that capturing it?
"Yes, exactly—they don't feel safe"
What alternatives are you seeing for creating more safety?
"Maybe exclude the manager and use a different format"
I hear two directions—environment and format. Which feels most compelling to you right now?
"The manager not being there—that's the biggest barrier"
Let's make this concrete. What exactly will you do? When will it happen, and how will you know if it worked?
"Run a 60-min retro Friday using 4Ls format, no manager. I'll ask 3 people afterward how it felt."
Perfect. That's clear and doable. You're committed to that?
Real coaching isn't one-dimensional. Start with quick facts, dive into learning, then explore the deeper "why"—all in the same session.
Direct teaching and clear instruction. Understands your context, then explains what to do, why it works, and how to implement it.
Documented patterns and practices from Agile thought leaders. Shares multiple approaches with full citations so you can choose what fits.
Powerful questions that help you explore current reality, generate alternatives, and tap into where you have energy. Ends with specific actions you'll actually complete.
Generic AI gives generic answers. pictor is purpose-built for Agile coaching.
The difference: ChatGPT is a general assistant. pictor is your dedicated Agile coach—understanding your context, tracking your growth, and helping you become the practitioner you want to be.
Whether you're new to Agile or a seasoned expert, pictor adapts to your experience level and role.
Just starting your Agile journey? Get clear explanations of practices, ceremonies, and frameworks without the jargon. Expert mode teaches you the fundamentals fast.
"I went from confused about sprint planning to running my first one confidently in a week."
Daily blockers, ceremony facilitation, team dynamics. Get instant answers when your team needs you most. All three modes help you navigate the challenges of servant leadership.
"My go-to when I need to solve a facilitation challenge between meetings."
Balancing stakeholders, prioritizing backlogs, making trade-offs. Mentor mode shares proven patterns from product leaders. Coach mode helps you work through tough decisions.
"Helped me think through stakeholder conflicts I couldn't discuss with my team."
Scaling transformations, coaching leaders, navigating organizational change. Access documented patterns from Lyssa Adkins, Team Topologies, and industry research.
"Like having a coaching supervisor available 24/7 for my toughest cases."
Leading technical teams with Agile practices. Navigate the intersection of technical excellence and team dynamics. Get guidance on velocity, estimation, and technical debt management.
"Bridges the gap between Agile theory and engineering reality."
You know Agile—now you're deepening expertise or exploring new frameworks. Mentor mode connects you to advanced patterns. Coach mode helps you discover your own insights.
"Finally, a tool that doesn't talk down to me. It meets me where I am."
pictor connects conversations to insights to action
Get unstuck through conversations. Expert answers, mentor guidance, or powerful coaching questions.
Weekly competency analysis shows where you're growing and what to focus on next.
Turn insights into commitments. Track what matters. Build the habits that drive growth.
Icons by Arief Mochjiyat and Kris.27 from Noun Project
While ChatGPT is a general-purpose AI, pictor is specifically trained on Agile methodologies and coaching techniques. Our three modes (Expert, Mentor, Coach) provide specialized coaching approaches that go far beyond simple Q&A—from Socratic learning to deep reflective coaching.
Tokens are units of text processing. As a rough guide: a typical conversation uses 10,000-20,000 tokens. The free tier (20k tokens) gives you 1-2 conversations to try it out. Ripper (200k) covers 10-12 conversations per month—perfect for regular use. Big Wave (500k) is ideal for entire teams or daily coaching.
Yes. Your conversations are encrypted in transit and at rest, never sold, and never used to train AI models. We use Row-Level Security (RLS) to ensure you can only access your own data.
Yes! That's one of pictor's unique strengths. You might start with Expert mode for quick facts, switch to Mentor mode to understand the "why," then move to Coach mode to explore implementation challenges—all in the same session.
Tokens reset monthly on your billing anniversary. You can see your real-time usage in your dashboard, so you always know where you stand. If you need more before the reset, you can upgrade to a higher tier anytime—the change takes effect immediately.