Honter - Run design projects like a studio, even if you’re solo
by•
Honter is a workspace built specifically for designers to collaborate with clients in a structured, professional way. Instead of juggling emails, PDFs and scattered comments, designers manage briefs, moodboards, versions, feedback, and deliveries in one clear flow. Each workspace is designed around how real design projects actually work. AI is used quietly in the background to help clarify client feedback and draft quick responses, so designers spend less time managing and more time designing.
Replies
Product Hunt
@curiouskitty
That’s exactly the risk we’re trying to avoid. Honter is not meant to sit next to everything else.
The clearest scenario where Honter replaces part of the stack is client-facing communication around the work itself.
Designers still design in Figma. They can still message internally on Slack if they want. But once a project starts, Honter becomes the single place where briefs, versions, feedback, and decisions live. That means no feedback in email, no “quick note” on WhatsApp, and no chasing comments across tools.
A successful first week looks like this:
For the designer:
One workspace per project.
The brief lives there, even if it evolves.
Each design version is uploaded there, and all feedback is tied to that version.
Fewer clarifying calls, fewer follow-ups, less second-guessing.
For the client:
One link, no account required.
They always know where to leave feedback.
They can see what changed, what was addressed, and what’s still open.
They stop asking “where should I send this?” entirely.
If Honter works, it doesn’t add a place to check.
It removes the need to check everywhere else.
Thank you for your question, we really appreciaate it
@umberto_abbatantuono
Thank you for your questions.
Pricing:
We’re finalizing it right now, but the plan is intentionally simple. One subscription in the $10–$15/month range that unlocks unlimited workspaces and full use of the AI assistant. No per-project or per-client complexity. We want pricing to feel predictable, not like another thing designers have to manage.
Access & security:
Honter uses shareable links to keep the guest experience frictionless. Anyone with the link can access the workspace, which is a deliberate tradeoff to avoid forcing client sign-ups.
That said, we’re actively adding more control, things like link expiration, access levels, and workspace-level privacy settings, so designers can dial in how open or restricted each project should be. The goal is flexibility without turning collaboration into a login nightmare.
Noodle Seed
Congrats on the launch @axeltdesign and co!
@saad_zafar
Thank you man, congrats to you as well, your product is doing really good!!
The version-tied feedback + “quiet AI” clarity check is a smart way to reduce mid-project drift 🔥
As you scale to bigger teams/clients, the gnarly bit is secure guest access + auditability across briefs/moodboards/versions best practice is signed, expiring share links + per-version immutable audit logs + granular roles (view/comment/approve).
Are you planning native Figma version linking/diffing (file+frame refs) and how will you handle revoking/rotating client links without breaking the frictionless flow?
@ryan_thill
Great points. A lot of the drift is already reduced today through enforced structure. In our branding workspace, the brief has to be completed before the moodboard unlocks, and a direction has to be approved before versions unlock, etc. That sequencing alone prevents many “who approved what” issues.
What we’re still evolving is the explicit audit layer on top of that flow. As teams and clients get bigger, approvals, feedback, and version decisions need to be clearly traceable over time. That’s where signed or expiring links, role-based access, and stronger approval records come in, without breaking the frictionless, no-signup experience.
On Figma, we’re not trying to replace it. The direction is native linking to the exact file or frame that was reviewed, so Honter becomes the system of record for decisions and feedback, while design stays in Figma. For access revocation, the goal is link rotation and scoped invalidation, so designers can change access without resetting the workspace or forcing re-onboarding.
We’re being intentional about layering control as needed, rather than turning collaboration into a heavy security workflow.
@axeltdesign Love the “structured gates” approach, that’s a clean way to make approvals implicit without adding friction.
For the audit layer, what’s worked well is an append-only decision log per artifact (brief, direction, version) with immutable events, plus a lightweight hash chain so edits/deletes are detectable, even if you later add stricter roles.
On the Figma side, tying feedback to exact file key + node-id (frame) plus optionally a version snapshot keeps Honter the system of record. Are you planning to also pin decisions to a specific Figma version when teams have it available, or always to “latest frame”?
@ryan_thill
Great question. Today, Honter handles this at the version level rather than directly inside Figma.
Each upload (image or PDF) creates a discrete version. Approvals are tied to that exact version and remain approved even if newer versions are uploaded later.
So if Version 5 is approved and a Version 6 is added, Version 5 stays approved and the new version requires its own decision.
Figma linking is something we’re exploring, but the core principle stays the same: approvals should always be tied to a specific artifact, never float to “latest.”
We’re starting with clarity and immutability first, then layering deeper integrations as needed.
Congrats on the launch! Love the “tap to match” model—feels like a cleaner, less noisy way to pair teams with genuinely great‑fit talent.
@zeiki_yu appreciate your comment man :=)
I like the overall idea! If you add lots of AI features for generating small routine design tasks, it could become an indispensable app. For example: copying style from a screenshot, generating forms/polls and other elements in the site’s style, automatically creating style guides or brand books with all the necessary elements, etc. There are many such tasks — designers spend 80% of their time on routine work, and AI could eliminate that.
@mykyta_semenov_
Totally agree on the problem. Designers lose a lot of time on routine work.
Our approach is to keep design creation in tools like Figma, and use AI to reduce friction around the process: clearer briefs, cleaner feedback, better versioning, and fewer back-and-forths.
AI as support, not replacement.
@axeltdesign I wasn’t suggesting replacing designers 🙂 For example, creating a style file from an existing design and transferring it to Figma is not a finished task — the designer still needs to manually edit that file and bring it to a final state, but that’s only about 20% of the work.
And this idea is based on a lot of experience working with design. We used to mainly build corporate systems, where design is endless sets of forms, lists, surveys, and other routine work. You do the main page once, where you actually think about the style, and then you replicate that design across 100–200–300 typical pages. And 95% of the work is pure routine.
The biggest takeaway from launch day so far is how much designers care about structure. Keeping briefs, direction, and versioned feedback in one place resonated more than adding more features.
Early feedback is already shaping the next steps, especially around onboarding clarity, access control, and keeping the AI helpful without being intrusive.
Really appreciate the thoughtful questions and honest reactions here. They’re directly influencing where Honter goes next.