back
Turning Spira’s onboarding data into product value
Turning Spira’s onboarding data into product value
7 min read · 3 days ago
7 min read · 3 days ago


How one onboarding answer could help Spira understand its users, while giving every user a more relevant path to their first post.
How one onboarding answer could help Spira understand its users, while giving every user a more relevant path to their first post.
Project snapshot
Type: Self-initiated concept redesign
Type: Self-initiated concept redesign
My role: Product designer: research, UX review, flow design, UI
My role: Product designer: research, UX review, flow design, UI
Scope: Onboarding → personalized first-content experience
Scope: Onboarding → personalized first-content experience
Tools: Figma & Claude
Tools: Figma & Claude
Based on: 20 captured screens of the live product. No user testing or analytics yet
Based on: 20 captured screens of the live product. No user testing or analytics yet
What is Spira?
What is Spira?

Spira is an AI tool for social media. It can make short videos, schedule posts, and show how they perform. Its website says it is “the AI that runs your entire social,” one place to create, post and grow a channel.
Spira is an AI tool for social media. It can make short videos, schedule posts, and show how they perform. Its website says it is “the AI that runs your entire social,” one place to create, post and grow a channel.
Why look at onboarding?
Why look at onboarding?
Spira already asks users an important question during onboarding: What are you looking to use Spira for?
Grow a personal brand. Create content for clients. Automate posting. And so on.
That information may already be valuable to Spira, helping the team understand who is signing up and what they came to accomplish.
But from the visible experience, that intent does not appear to meaningfully shape what happens next. After answering, users arrive at a library of tools (Spira Maxima, Asset Generator, AI Shorts, AI Podcast, Slideshow, and more) and still have to decide which one will get them to their goal.
That raised a question:
If users are already telling Spira why they’re here, could that answer become useful to them too?
Spira already asks users an important question during onboarding: What are you looking to use Spira for?
Grow a personal brand. Create content for clients. Automate posting. And so on.
That information may already be valuable to Spira, helping the team understand who is signing up and what they came to accomplish.
But from the visible experience, that intent does not appear to meaningfully shape what happens next. After answering, users arrive at a library of tools (Spira Maxima, Asset Generator, AI Shorts, AI Podcast, Slideshow, and more) and still have to decide which one will get them to their goal.
That raised a question:
If users are already telling Spira why they’re here, could that answer become useful to them too?


One input, two purposes
One input, two purposes
Instead of treating onboarding only as something to complete, I explored using the user’s answer as product context.
For Spira: the answer can remain a useful signal for segmentation, research and understanding use cases.
For the user: the same answer can immediately personalize what Spira recommends and where it takes them next.
Answer → intent understood → experience adapts.
The idea isn’t to remove useful data collection. It’s to return value from the data users already give.
One note: I can only see the public product, not how Spira uses this data internally. The research and segmentation use is a hypothesis, not a confirmed fact.
Instead of treating onboarding only as something to complete, I explored using the user’s answer as product context.
For Spira: the answer can remain a useful signal for segmentation, research and understanding use cases.
For the user: the same answer can immediately personalize what Spira recommends and where it takes them next.
Answer → intent understood → experience adapts.
The idea isn’t to remove useful data collection. It’s to return value from the data users already give.
One note: I can only see the public product, not how Spira uses this data internally. The research and segmentation use is a hypothesis, not a confirmed fact.
How I approached it
How I approached it
Reviewed 20 screens across onboarding, tools, editor, projects, calendar, analytics, brand setup and pricing.
Reviewed 20 screens across onboarding, tools, editor, projects, calendar, analytics, brand setup and pricing.
Looked for friction at each step: what is the user asked to decide, and what happens next?
Looked for friction at each step: what is the user asked to decide, and what happens next?
Wrote a UX review with five findings, each marked as an observation, a hypothesis, or a proposed change. I was careful not to claim facts a screenshot can’t prove.
Wrote a UX review with five findings, each marked as an observation, a hypothesis, or a proposed change. I was careful not to claim facts a screenshot can’t prove.
Picked a starting point: guided activation and project continuity, because they improve almost every existing feature.
Picked a starting point: guided activation and project continuity, because they improve almost every existing feature.

A short version of each:
Goal-to-action activation (High): A chosen goal should become a first task.
Goal-to-action activation (High): A chosen goal should become a first task.
Project continuity (High): One piece of work should survive every tool handoff.
Project continuity (High): One piece of work should survive every tool handoff.
Context-aware empty states (High): Empty Projects, Calendar and Analytics pages should point to the next useful step.
Context-aware empty states (High): Empty Projects, Calendar and Analytics pages should point to the next useful step.
Shared brand context (Medium): Approved brand details should be reused everywhere.
Shared brand context (Medium): Approved brand details should be reused everywhere.
Clear generation decisions (Medium): Show what will be made and what it costs before the user commits credits.
Clear generation decisions (Medium): Show what will be made and what it costs before the user commits credits.
The first finding, goal-to-action activation, is where the “one input, two purposes” idea became a design hypothesis.
The first finding, goal-to-action activation, is where the “one input, two purposes” idea became a design hypothesis.
The hypothesis and the core idea
The hypothesis and the core idea
I explored a simple hypothesis:
If Spira turns a user’s stated goal into their first recommended task, new users may reach useful content with fewer decisions.
The onboarding answer becomes persistent context rather than a temporary form response.
Don’t onboard users into the product. Onboard them into their first successful outcome.
If someone picks “Grow my personal brand,” Spira should say: let’s make your first post. Give me a topic, I’ll recommend the format, and we’ll make a draft.
Success isn’t “opened a tool” or “started generating.” It’s a usable piece of content.
I explored a simple hypothesis:
If Spira turns a user’s stated goal into their first recommended task, new users may reach useful content with fewer decisions.
The onboarding answer becomes persistent context rather than a temporary form response.
Don’t onboard users into the product. Onboard them into their first successful outcome.
If someone picks “Grow my personal brand,” Spira should say: let’s make your first post. Give me a topic, I’ll recommend the format, and we’ll make a draft.
Success isn’t “opened a tool” or “started generating.” It’s a usable piece of content.
I set three rules for the first release:
Start from the goal, not a catalogue.
Start from the goal, not a catalogue.
Save the work automatically as a project, so nothing is lost.
Save the work automatically as a project, so nothing is lost.
Always show the next useful step after each stage.
Always show the next useful step after each stage.

The new flow
The new flow
The flow has six screens after sign-up. It’s the first application of the idea: each screen asks for one thing and uses the answer on the next screen.
The flow has six screens after sign-up. It’s the first application of the idea: each screen asks for one thing and uses the answer on the next screen.
1. Goal
One question: “What should Spira help you with first?” Four clear options, plus a box to describe something else. There is a quiet “All tools” exit for experienced users.
One question: “What should Spira help you with first?” Four clear options, plus a box to describe something else. There is a quiet “All tools” exit for experienced users.

2. Context
“Where will your first post live?” Spira asks for the platform (Instagram Reels, TikTok, YouTube Shorts, LinkedIn, Instagram post, X) and “What are you known for?” The user can also paste a LinkedIn, Instagram or website link and let Spira read it.
“Where will your first post live?” Spira asks for the platform (Instagram Reels, TikTok, YouTube Shorts, LinkedIn, Instagram post, X) and “What are you known for?” The user can also paste a LinkedIn, Instagram or website link and let Spira read it.

3. First task
“Let’s create your first Reel.” Spira suggests topic ideas based on the profile, such as “The pricing mistake that cost us our first 10 customers.” The user can also write their own idea or paste a script.
“Let’s create your first Reel.” Spira suggests topic ideas based on the profile, such as “The pricing mistake that cost us our first 10 customers.” The user can also write their own idea or paste a script.

4. Plan
This is where Spira makes the tool choice so the user doesn’t have to. It recommends a Talking Reel (9:16, about 30 seconds) and shows the plan: script, presenter, captions and sound. Each part has a “Change” option. Other formats (Carousel, Text-on-screen video, Use my own footage) are one tap away. The credit cost is shown before generating: “150 of your 500 free credits.”
This is where Spira makes the tool choice so the user doesn’t have to. It recommends a Talking Reel (9:16, about 30 seconds) and shows the plan: script, presenter, captions and sound. Each part has a “Change” option. Other formats (Carousel, Text-on-screen video, Use my own footage) are one tap away. The credit cost is shown before generating: “150 of your 500 free credits.”

5. Draft
The script appears first while the video is still rendering, so users can start reviewing right away. Quick chips like “Punchier hook” and “Make it shorter” let them refine without starting over. Power users can open the full editor.
The script appears first while the video is still rendering, so users can start reviewing right away. Quick chips like “Punchier hook” and “Make it shorter” let them refine without starting over. Power users can open the full editor.

6. Ready
“Your first Reel is ready.” It’s saved to Projects. The user can download the video, post to Instagram, or schedule it. Under “Next,” Spira offers to make three more for the week in the same voice and format.
“Your first Reel is ready.” It’s saved to Projects. The user can download the video, post to Instagram, or schedule it. Under “Next,” Spira offers to make three more for the week in the same voice and format.

Try the prototype
Try the prototype
Key design decisions
Key design decisions
Spira picks the tool, not the user. People came for an outcome, not a tool name. The tool still runs underneath, and every choice can be changed.
Spira picks the tool, not the user. People came for an outcome, not a tool name. The tool still runs underneath, and every choice can be changed.
Experts aren’t trapped. “All tools” is always visible, and the full editor is one click away.
Experts aren’t trapped. “All tools” is always visible, and the full editor is one click away.
The referral question moves later. “How did you hear about us?” may be useful to Spira for acquisition insight, but it does not need to interrupt the first content task. It can appear after the user reaches first value.
Costs are visible before generating. Showing the credit cost at the plan step builds trust. I didn’t invent exact prices or wait times. Those should come from Spira’s real policies.
Every answer gets used. The goal sets the voice, the platform sets the format, and the idea sets the plan. Edits to the draft can teach Spira the user’s taste for future posts.
The work is saved. The finished Reel goes straight to Projects, so it’s not lost if the user leaves.
The referral question moves later. “How did you hear about us?” may be useful to Spira for acquisition insight, but it does not need to interrupt the first content task. It can appear after the user reaches first value.
Costs are visible before generating. Showing the credit cost at the plan step builds trust. I didn’t invent exact prices or wait times. Those should come from Spira’s real policies.
Every answer gets used. The goal sets the voice, the platform sets the format, and the idea sets the plan. Edits to the draft can teach Spira the user’s taste for future posts.
The work is saved. The finished Reel goes straight to Projects, so it’s not lost if the user leaves.
The bigger opportunity
The bigger opportunity
The idea doesn’t have to end after onboarding.
Once Spira understands why someone is here, that context could gradually influence:
Home recommendations → creation paths → templates → empty states → suggested ideas → projects → recurring content.
Brand DNA can add another layer:
Who are you? + What are you trying to achieve? + What does your brand sound like?
So the long-term concept isn’t just personalized onboarding. It’s a Spira that progressively understands why you’re here and uses that context throughout the product.
The idea doesn’t have to end after onboarding.
Once Spira understands why someone is here, that context could gradually influence:
Home recommendations → creation paths → templates → empty states → suggested ideas → projects → recurring content.
Brand DNA can add another layer:
Who are you? + What are you trying to achieve? + What does your brand sound like?
So the long-term concept isn’t just personalized onboarding. It’s a Spira that progressively understands why you’re here and uses that context throughout the product.
How I’d know it works
How I’d know it works
I haven’t tested this, so I’m not claiming results. Here is what I would measure and how I’d test it.
I haven’t tested this, so I’m not claiming results. Here is what I would measure and how I’d test it.
Measures:
Time to first usable draft
Time to first usable draft
Onboarding-to-first-draft conversion
Onboarding-to-first-draft conversion
How often users go back and forth between tools
How often users go back and forth between tools
First draft to first scheduled or published post
First draft to first scheduled or published post
Usability test: Ask new users to “create a post for your brand that you would actually use.” Watch for hesitation, switching tools, repeated inputs, lost work, and whether they finish. The goal is to find where people get stuck: choosing a path, producing a usable result, or reaching publish/export.
Usability test: Ask new users to “create a post for your brand that you would actually use.” Watch for hesitation, switching tools, repeated inputs, lost work, and whether they finish. The goal is to find where people get stuck: choosing a path, producing a usable result, or reaching publish/export.
One comparison: Does goal-based personalization outperform the existing tools-first experience?
One comparison: Does goal-based personalization outperform the existing tools-first experience?
Current: onboarding → tools catalogue
Current: onboarding → tools catalogue
Concept: onboarding → recommended first task
Concept: onboarding → recommended first task
Compare time to first usable draft, completion, tool switching and backtracking, publish/export completion, and whether the recommendations feel relevant to the user.
Compare time to first usable draft, completion, tool switching and backtracking, publish/export completion, and whether the recommendations feel relevant to the user.
Takeaway
Takeaway
Spira was already asking the right question.
The opportunity wasn’t necessarily to remove onboarding or collect less information. It was to make that information useful.
By turning stated intent into product context, the same interaction can serve two sides: Spira learns why people are here, while users get an experience that better understands why they’re here.
Onboarding becomes more than a form before the product.
It becomes the first input into the product itself.
This is an independent concept project made from screenshots of the public product. It is not affiliated with or endorsed by Spira.
Spira was already asking the right question.
The opportunity wasn’t necessarily to remove onboarding or collect less information. It was to make that information useful.
By turning stated intent into product context, the same interaction can serve two sides: Spira learns why people are here, while users get an experience that better understands why they’re here.
Onboarding becomes more than a form before the product.
It becomes the first input into the product itself.
This is an independent concept project made from screenshots of the public product. It is not affiliated with or endorsed by Spira.
More case studies.
More case studies.

Sending Idle EV Wallet Money to Family, Without the Hassle
Sending Idle EV Wallet Money to Family, Without the Hassle
Oct 22, 2026
Oct 22, 2026

Simplifying a New Financial Payment Model
Simplifying a New Financial Payment Model
Oct 22, 2026
Oct 22, 2026