At Pulsian, I lead strategy and Design for a platform to discover AI resources and evaluate how to use them at work, based on each company’s goals and constraints.
My role
Product strategy and Design leadership
Scope
Market and business · UX/UI · Content · Implementation
Current stage
Documented strategy and interactive interface
Timeline · AI newsCockpit · Usage scenario
In the Timeline, users select a story to see a summary, sources and a suggested application. This screen shows a demonstration scenario for a fictional company called Nexo Digital, using prepared example content.Enlarge image ↗
Product screenshots show the interface in Portuguese.
How I defined the audience, proposition and business model
Professionals find AI news, tools and recommendations across many channels. Pulsian’s challenge is to help them identify options that could serve their work, taking their goals, available resources and decisions into account.
I lead the product from market research to interface implementation. I structured desk research on the market and competitors, audience profiles and work needs (Jobs to Be Done), the value proposition and business model scenarios. This work guides priorities, content and UX/UI decisions.
The priority audience is professionals and leaders evaluating AI for products, operations and company competitiveness. I combined two ways to use the product: discovering resources freely and comparing options for a specific need. Users can start with a news story or a work question.
Market and competitors
I compared newsletters, content readers and AI assistants by value proposition, features and commercial model. Pulsian’s proposition combines resource discovery, organized knowledge and evaluation of options for each work situation.
Audience and work needs
I mapped situations where professionals need to stay informed, discover tools or evaluate AI applications. I considered their responsibility for decisions, as well as job title, to prioritize usage scenarios.
Business model and costs
I modeled free and paid offers, revenue, processing costs, human review and margins. These simulations help define what to offer and how to expand the product, accounting for the cost of personalization and intensive usage.
Features and tests
I organized proposed features, their dependencies and assumptions to test into a product strategy and validation plan. The priority is to explain the product’s value, assess interest in specific applications and expand operations based on findings.
02Product organization
News, tools and analyses in three areas
A news story can bring someone to the product, but not every need starts with a launch. An existing tool may solve a current problem. I therefore organized navigation to support both resource discovery and comparison of options.
I created three complementary areas: Timeline, Arsenal and Análises. Timeline brings together news; Arsenal organizes tools, models and resources; Análises supports evaluating alternatives for a work need. Users choose where to start, without following a mandatory sequence.
Timeline
Follow AI news
News organized by date, with summaries, sources and possible applications.
Arsenal
Discover AI resources
Tools, models, APIs and capabilities organized by relevance to work, beyond their launch date.
Análises
Compare alternatives
AI application options compared against goals, criteria, costs, risks and constraints.
In Pulsian, “context” means the goals, available tools and constraints of users and their companies. This information helps assess which content and alternatives are relevant.
03Content and interaction
From a news story to a possible use at work
In Timeline, selecting a story opens a summary in the side panel. The “Ver briefing” button shows more detail and a possible application for the company. In the Nexo Digital example, the briefing suggests evaluating an AI agent to support competitor research.
I designed the flow to show a summary first, with details one click away. The briefing separates the original announcement, Pulsian’s interpretation and a suggested next step. Sources let users check the announcement. Users then assess whether the interpretation and suggestion apply to their company.
Briefing opened from the TimelineEnlarge image
The briefing opens over Timeline. Users can read the details and return to the news list without leaving the page.Enlarge image ↗
News
What was announced and which sources support the information.
Interpretation
How the development relates to the goals of the fictional company Nexo Digital, used in this demonstration scenario.
Next step
A suggested test or evaluation, with conditions to check.
04Revising an analysis
How a new requirement changes the recommendation
In Análises, users compare AI alternatives for a work need and can revise the recommendation when conditions change. I prepared a demonstration: a team needs to summarize customer service interactions. The first version suggests testing the same sample in Claude and ChatGPT.
Adding a requirement to prioritize the company’s existing Microsoft 365 tools changes the next step: check Copilot access, licenses and permissions. I designed the interface to show the new requirement, record the revised recommendation and keep the previous version accessible. Users can compare the guidance and understand why it changed.
Need and conditions
Summarize customer service interactions and compare tools for the task.
Suggested next step
Test the same sample in Claude and ChatGPT.
Version 1 · Comparing toolsEnlarge image
The first version proposes a comparative test before choosing a tool.Enlarge image ↗
Need and conditions
Summarize the interactions using the company’s existing Microsoft 365 setup.
Suggested next step
Check Copilot access, licenses and permissions.
Version 2 · Using the existing setupEnlarge image
The new condition changes the next step. The interface records the revision and keeps the previous version available.Enlarge image ↗
History lets users compare recommendations and check which conditions changed in each analysis.
05Interface design and implementation
From wireframes to the implemented interface
I led UX/UI work from wireframes to implementation. The studies explored navigation, analysis presentation and access to previous versions. I refined the interface to highlight the recommendation, make its supporting criteria easier to find and distinguish selection, revision and history.
I documented colors, typography, spacing and reusable components. I also worked on content, contrast and adaptation to different screens. I use AI for implementation while retaining direct responsibility for Design decisions, code review and the quality of the delivered interaction.
Wireframe of analysis revision and historyEnlarge image
A wireframe from an earlier stage of the project, using a different scenario from the examples above. The study shows how to present a revised analysis and keep the previous version accessible when a constraint changes.Enlarge image ↗
Visual hierarchy
Highlight the recommendation and provide access to the criteria behind it.
Version history
Keep revision and access to earlier versions alongside the analysis.
Visual consistency
Reuse color, typography, spacing and component patterns.
06Deliverables and next steps
What is ready and what still needs testing
Pulsian has a documented strategy and an interactive interface that demonstrates the product proposition. Decisions about the market, audience, business model and priorities guide navigation, flows and screens.
The next step is to test the experience with users in real work situations. The plan is to check whether they understand the flows, find recommendations useful and are interested in analysis features. The conditions needed to operate the product will also be assessed.
Completed deliverables
Market and competitor desk research, audience profiles and work needs, value proposition, economic scenarios, product strategy and validation plan. Published product website and interactive cockpit, with documented wireframes and interface patterns.
Next tests and improvements
Test flows with users, identify when analyses help with work decisions and assess interest in the proposed features. Use the findings to guide personalization and content operations.
Development stage: the cockpit presents example scenarios and content. Real-time AI personalization and continuous intelligence operations are development areas; demand and economic viability will be assessed through user testing.