Still doing every
onboarding yourself?
Turn your walkthrough into an onboarding guide inside your product. Help clients find their next step, get an answer, or confirm a supported action.
Early prototype · exploring first pilots
Record once.
Guide the next client.
You teach the path.
Your guide stays with the client.
Hi. Let’s find
your next step.
Choose the kind of help
you need.
Fictional example · simulated interaction
One journey. Different ways to help.
A guide inside your product, ready to point, listen, or wait for permission. Try the fictional workflow below to see how the experience could feel.
Create your first report
Choose the data you want to bring into view.
Open a new report. Your connected source is ready to use.
A little direction,
right where it helps.
Show the relevant control, explain the next step, and bring in the useful moment from your walkthrough.
- Start from the client’s actual progress.
- Skip the steps already completed.
- Let the client carry out the action.
A finished tour is not the goal. A useful result is.
Your onboarding conversation
Create a first report.Choose your connected source, then the information you want to see. We can walk through that together.
A configured email can bring the client back to this step. Cancel it when they make progress.
Keep the conversation
with the context.
Answer the question in front of the client, then help them resume when they’re away from your product.
- In-app chat tied to the current task.
- Email follow-ups with timing and stop rules.
- One shared journey across sessions.
Follow-ups should reflect progress, not just the calendar.
A supported actionSimulation
I can prepare
the first draft.
Create one sample report using the connected source. Nothing will be shared or published.
This changes the local example only. No real account or data is connected.
Will this publish anything?
No. This example creates a local draft only. In your product, the guide explains the actual change before asking for permission.
Help can do the work.
You set the limits.
Offer a supported action, explain what will change, and let the client choose. The product checks permissions and verifies the result.
- Only actions you explicitly enable.
- The client’s existing permissions apply.
- A clear handoff when the agent cannot act.
Try the member role to see the permission boundary.
Interactive demonstration · Harbor Metrics is fictional · actions and answers on this page are simulated.
You know the way.
Teach it once.
Start with your onboarding video and a description of your product. Valkyriai generates actions and a journey; you connect the context and permissions that make them useful.
Watch the concept filmOne video is the starting point.
Context, milestones and permissions make the journey work.
- 1
Show the path
Upload your walkthrough and describe your product. Show the first useful result, the prerequisites and how to get there.
- 2
Generate your journey
The prototype turns your video and description into actions and a saved journey. Review or edit the result whenever you need to.
- 3
Connect your product
Use the frontend SDK to connect user context and relevant progress. Wire up verified outcomes and any supported actions.
- 4
Choose how to help
Choose the guidance and supported actions for your first workflow. Preview the happy path, permission checks and handoff before a pilot.
A specific job.
The platform and SDK foundation are running in a local prototype. A pilot still needs a trusted connection to your product, reliable success checks and production setup. We’ll measure that effort alongside the time it could save.
Stay close to the work
that needs you.
The aim is less repetition, with the important conversations still reaching you. Know what happened before you step in.
- See the blocker and what was already tried.
- Take over without losing the client’s progress.
- Correct a step, pause a journey, or disable an action.
Source access is missing.
The client connected their account, but the source owner still needs to grant read access.
- Already tried
- Explained the prerequisite and showed the relevant walkthrough step.
- Next useful step
- Ask the source owner for access. Keep the client’s setup progress.
Agent action paused for a person
Illustrative founder handoff
For the founder
still doing the onboarding.
Whether clients sign up themselves or start with a call, the opportunity is the same: a recurring path you can explain, observe and improve.
When clients start on their own
Help them past the unfamiliar screen, the unanswered question, or the setup step they left for later.
Self-serve SaaSWhen every account starts with you
Carry the walkthrough forward after the call, with progress and blockers visible when you need to step in.
Sales-assisted SaaSBest explored around a repeatable setup path. Bespoke implementations, missing product features and missing authority still need a person.
See a clear
next step.
Follow a fictional Harbor Metrics client from a blocked connection to a first report.
This earlier concept film explores the guidance flow. It is a simulation, not a recording of working software.
Read the transcriptWhat do you keep
explaining?
Let’s start with one workflow you still walk every client through.
- Show us the task and where clients get stuck.
- Work out what can be guided, answered or safely supported.
- Agree a pilot scope, success criteria and price before starting.
Valkyriai is an early prototype. We’re exploring first pilots around repeatable SaaS setup. No payment is collected here.
Talk to Federico by emailTell us about your workflow.
The request form is hosted by Tally. Load it here or open it in a new tab. Your answers are saved when you submit.
Privacy & contact · Please leave out passwords and client data.
A few clear
answers.
What the concept includes, and what still needs to be built.
Can I install valkyriai today?
Valkyriai is an early prototype, with a local platform, SDK foundation and video-to-journey generation. It is not a public self-serve service yet. Let’s discuss one workflow and the integration needed for a first pilot.
Is one video really enough?
Your walkthrough and product description are the main teaching inputs. The prototype generates and saves actions and journeys automatically. You can review and edit them; a real integration still needs product context, permissions and a reliable definition of success.
What would my team need to integrate?
The SDK foundation connects an onboarding configuration to a product interface. Your product must supply trusted identity, progress signals and permitted actions. Secure actions may also need a backend connection. We would scope and measure this work in a pilot.
Can the agent take actions in my product?
The prototype includes an action runtime; a live product integration still needs to be connected and tested. You enable the supported actions. The client confirms a proposed change, the product enforces their permissions, and success must be verified. The actions on this page are simulated.
How would email follow-ups work?
You would configure the sender, triggers, timing and stop rules. Messages should reflect the client’s current progress and return them to the relevant step. Completion, opting out or a founder taking over should stop conflicting follow-ups. The email service is not implemented yet.
What happens when it cannot help?
The intended behavior is to preserve progress, explain the blocker and bring a person the relevant context and steps already tried. Missing authority, product gaps and uncertain outcomes are reasons to stop and hand over.
How much will it cost?
Pricing is not set. A paid pilot would have a specific workflow, delivery scope, success criteria and price agreed before it starts. There are no savings or completion guarantees.
