Neartail - ChatGPT Apps
2025Create forms inside ChatGPT and instantly publish them across platforms.
BuddyHQ.AI
Your customers are already saying incredible things about your product. BuddyHQ turns that voice video, audio, text into branded, publish-ready UGC content. No editing suite. No copywriter. Just feedback in, marketing assets out.
I'm Live!
Website Link
.png)
30-second overview
- A 0→1 AI SaaS product. BuddyHQ is a content engine that turns raw customer feedback into branded marketing assets across 7+ formats.
- I led design end-to-end on the MVP, from discovery to production specs. Defined the conversational interface, the content pipeline, and the three-tier storage system that became the product's backbone.
- Built and pre-release. Validated with 4 marketing professionals; greenlit for partner-facing rollout.
PRODUCT
WEB PLATFORM
SaaS application
TIMELINE
JAN 2025 – MAY 2025
5 months
TEAM
LED DESIGNER
2 Full-stack engineer, founder & co-founders
Problem
Hours of customer voice. Zero content.
Imagine you're a marketing lead at a B2B SaaS company. You just wrapped a customer interview series. 14 video calls, 200+ survey responses, three months of support transcripts in a Google Drive folder.
Every conversation has a quote, a moment, a story worth publishing. By Friday, you'll ship two LinkedIn posts and one case study draft. The rest sits untouched until someone deletes the folder next quarter.
The signal is there. The system to turn it into content isn't. Every asset travels through 5+ handoffs across 4+ tools manually, every time:
1
Collect
Survey tools drop responses into spreadsheets.
2
Review manually
A marketer watches hours of footage. Most signal gets lost here.
3
Brief the team
Summaries get handed to copywriters and designers. Context dilutes.
4
Build assets
Videos in Premiere, posts in Canva, emails elsewhere. Nothing shares context.
5
Scatter and lose
Final assets live across Drive, Notion, Dropbox. No source of truth.
3–7D
Average time
per content batch
per content batch
4+
Tools involved
per asset
per asset
5+
Handoffs
before publish
before publish
~80%
Customer feedback
never used
never used
My Note
It looks like a content problem. It's a system problem. Teams aren't short on tools, they're operating across disconnected systems with no continuity.
Vision
BuddyHQ says: let me turn your customers' words into your best campaigns.
What if customer voice didn't sit in folders, but flowed directly into the content marketing teams ship?
BuddyHQ ingests feedback in any modality video, audio, text, surveys, transcripts. An AI engine handles transcription, theme extraction, and brand voice calibration. It returns 7+ branded formats ready to publish. One pipeline. One interface. Zero tool switching.
Challenges
When I joined, there was no product. Just an AI engine.
The team had a working AI pipeline that could ingest video, audio, and text and generate multiple output formats. What they didn't have was a product around it. No interface. No information architecture. No defined user journey.
The questions I had to answer:
- Who is this for, and what specifically do they need it to do?
- How do you design one interface for an AI that produces 7+ content types from a single input?
- How do you hide AI complexity while still giving users meaningful control?
- Where does content go after it's generated, and how do teams reuse it?
Research & Discovery
So we started with a discovery sprint.
Before touching Figma, I ran a focused 5-day sprint to understand who BuddyHQ was actually for and how they'd use it. The goal was to validate the product hypothesis with real marketing teams before committing to a direction.
Discovery sprint plan
DAY 1
MAP
Stakeholder alignment, current workflow audit
DAY 2
INTERVIEWS
SME sessions with 4 marketing professionals
DAY 3
SKETCH
Concept exploration and information architecture
DAY 4
DECIDE
Synthesize findings, lock direction with team
DAY 5
VALIDATE
Test prototype concepts with 5 PoC users
SME interviews, what marketers actually said
I ran a lot of sessions with content marketers, growth leads, and content managers across SaaS companies. The conversations were more specific than I expected. Three breakdowns came up in every session:
- Fragmented tools → broken workflows. “It's not that any one tool is bad. It's that nothing talks to anything else.”
- Context loss → degraded quality. “By the time the post is written, it doesn't sound like the customer at all.”
- No reuse layer → lost compounding value. “We made a great asset last quarter. I have no idea where it is now.”
Personas
Vishwa
Marketing Lead (B2B SaaS)
I have hours of interviews. I just want a finished LinkedIn post that sounds like the customer.
Arun
Solo Content Creator
I'm a team of one shipping across five channels. I need leverage, not another tool to learn.
Delivering the Proof of Concept
After the discovery sprint, we shipped a clickable PoC.
The PoC validated the conversational-first model with real users and gave the team a concrete artifact to align on. I designed and prototyped the core interaction loop: upload feedback → describe intent → review generated content.
PoC validation results
I tested the prototype with 5 marketing teams from the SME pool. The findings unblocked the next phase:
5/5
Teams completed
core task unaided
core task unaided
~45s
Avg time
to first output
to first output
4.6/5
Would use
this tomorrow
this tomorrow
0
Required
onboarding steps
onboarding steps
⚠ Disclaimer: Early validation signals from a controlled PoC (n=5). Metrics indicate directional usability and adoption potential, not production-scale outcomes.
Defining the MVP
From PoC to scalable modules.
The PoC validated the concept. The real challenge was figuring out: which modules should we build first, and how could they flex across content formats without fragmenting into five separate products?
From the SME interviews and PoC sessions, the priority was clear:
- Marketing leads wanted quick generation from a single source minimum effort, maximum output.
- Content managers wanted flexibility across formats - video, post, email, blog, audio without learning five interfaces.
- Both groups wanted reuse. “I want to find that asset I made last quarter without searching three tools.”
That shaped the MVP into 6 core modules, each reusing the same generation engine, the same component patterns, and the same content storage system.
Strategic decision
The modules aren't five products. They're five views into the same engine. One source of truth, multiple surfaces. This was the architectural choice that made BuddyHQ scalable.
Core Feature #1
AI Chat Command Centre: The front door of the product.
WHY IT MATTERED
SMEs described their work as delegation, not configuration: "I need someone to take these responses and make a post." A chat-first model honored that mental model.
HOW I SOLVED IT
A single chat surface with five quick-action cards (Video Snippets, Survey Snap, Post Creator, Audio Bites, Blog). The AI handles orchestration — no menus, no settings before generating.
STRATEGIC VALUE
New output formats can be added as quick-action cards without redesigning the interface. The interaction model holds regardless of how the AI engine evolves underneath.
Core Feature #2
Video Snippets: Generated instantly, editable inline.
WHY IT MATTERED
Video was the most labor-intensive content type Premiere, CapCut, hours of clipping. Inline editing was the most-requested capability in interviews. Without it, marketers would still leave the app to finish the work.
HOW I SOLVED IT
A thumbnail strip showing all 10 generated snippets, inline captions for accessibility, and a built-in timeline editor for trim and approve. Platform resize (YouTube, Instagram, LinkedIn) lives in the same panel users never leave the canvas.
STRATEGIC VALUE
The timeline editor became the pattern for inline editing across every other module trim audio, edit blog, refine post all use the same component vocabulary.
Core Feature #3
Post Creator: One asset, multiple formats.
WHY IT MATTERED
Marketers ship the same post across LinkedIn, Instagram, and X three aspect ratios, three rounds of design work. The PoC confirmed format-switching was the second-biggest time sink after video.
HOW I SOLVED IT
Brand-consistent generation with one-click aspect-ratio switching. Source attribution baked in marketers can see exactly which customer quote drove the asset. A slide strip shows all variants; new pages can be added without re-prompting.
STRATEGIC VALUE
The aspect-ratio system became the foundation for any future format expansion ads, reels, carousels all use the same canvas with different output specs. Brand kit lives at the project level, so consistency holds without per-asset configuration.
Core Feature #4
Audio Bites: Voice as a first-class output, not an afterthought.
WHY IT MATTERED
Audio was the most overlooked format in early concept testing, but marketers requested it for two reasons: shareability (podcast clips, social audio) and accessibility (a second surface for the same content).
HOW I SOLVED IT
A dual-input system: audio extracted from video, or generated from text with brand voice calibration. One waveform editor, one transcript, one export regardless of source. Speaker-labeled transcripts, trim points, and brand audio styling (intro/outro) all in one panel.
STRATEGIC VALUE
Audio Bites became cross-module infrastructure. The same generated bites feed back into Video Snippets as background scores closing a loop other tools never close. One generation pass produces a podcast clip, a social audio post, a video soundtrack, and an accessible audio version of a blog.
Core Feature #5
Long-Form Editor: Emails & blogs, end-to-end.
WHY IT MATTERED
Generation alone wasn't enough every long-form piece needs editing. If users had to copy text into Google Docs to refine, the value of in-app generation collapsed.
HOW I SOLVED IT
An inline rich-text editor with a contextual toolbar. Toolbar placement was the hardest design call in the build I tested fixed-top, sidebar, and contextual-on-selection. Final placement docks away from the canvas and surfaces only on selection. The principle: the tool should never compete with the work.
STRATEGIC VALUE
Establishes BuddyHQ as a production tool, not a draft tool. The editor pattern extends to email composition and any future text-based content type. Users finish the work in BuddyHQ they don't pass it through three other tools to publish.
Core Feature #6
Global Library: The single source of truth.
WHY IT MATTERED
SME research surfaced one recurring complaint: “I made a great asset last quarter. I have no idea where it is now.” Without a reuse layer, every piece of content becomes a one-time output. Compounding value never accrues.
HOW I SOLVED IT
I proposed a three-tier hierarchy mid-project, in a team design review: Chat → Project → Library. The Library is a single searchable surface across the entire workspace, with filters by type, approval status, and project.
STRATEGIC VALUE
The most underestimated feature in the product. The Library is what makes BuddyHQ a platform, not a tool. It scales from one user to an enterprise team without architectural redesign and it's the foundation for future search, recommendations, and AI-powered reuse suggestions.
Impact & Outcomes
What was built. What was validated.
BuddyHQ is built and pre-release. The honest story is about what was designed, validated, and shipped. Not paid-customer metrics that don't yet exist. Here's what's real:
6
Core modules shipped end-to-end. Chat Centre, Video Snippets, Post Creator, Audio Bites, Long-Form Editor, Global Library. All built and integrated with the AI engine, ready for pre-release.
7+
Content output formats video snippets, social posts, emails, blogs, audio clips, UGC pages, and platform-specific resizes. All from a single unified interface.
12
Marketing professionals interviewed across SME sessions and PoC validation. Conversational-first interaction model validated with 5/5 teams completing core tasks unaided.
~45s
Average time to first output in PoC testing versus 3–7 days in the existing manual workflow. Stakeholder validation greenlit the next phase of partner-facing rollout.
Takeaways
What I took away.
1
Designing for scale starts on day one.
The three-tier hierarchy and modular components weren't add-ons they were the foundation. Strategic systems thinking turned a tool into a platform.
2
AI products are about trust, not automation.
Mid-project, I had real doubts about the AI premise. Working through that tension made me design for augmentation, not replacement. Every screen is built around a human making the final call.
3
The hardest problems aren't the biggest features.
The toolbar placement consumed more debate than any major flow. Friction lives in the details.
4
The best structural decisions came from conversations, not planning.
The three-tier hierarchy emerged from a mid-project design review the kind of decision that only happens if you're paying attention to what's breaking, not just what's been scoped.
