I Was Tired of Repeating Myself, So I Built an AI Version of Me

Areef Syed — Mon, 02 Feb 2026 02:45:28 +0000

Every developer with a portfolio knows this moment.

Someone visits your site.

They like your work.

Then they DM you and ask the same three questions you have already answered everywhere.

“Are you available?”

“What tech stack do you use?”

“Can you share your resume?”

After answering these for the 127th time, I thought, what if my website could just talk back?

That is how Klyro was born.

The Problem

Most websites are still built like digital brochures.

Click here. Navigate there. Scroll forever.

But people do not want to search.

They want to ask.

We are clearly moving into a conversational era. From support bots to AI assistants, users prefer typing a question over digging through menus. UX and support research across tools consistently shows that quick conversations often outperform deep navigation trees.

So I asked myself, why does my portfolio still behave like it is 2012?

The Idea

Klyro is an AI assistant that sits on your website and answers questions about you or your product.

Instead of:

“Read my about page”
“Check my projects tab”
“Download my resume”

Visitors can simply ask:

“Who are you?”
“What projects have you built?”
“Are you available for freelance?”
“How can I book time with you?”

And they get instant, contextual answers.

It is essentially an AI powered conversational layer on top of your personal or product knowledge base.

What Klyro Actually Does

At its core, Klyro:

Ingests your data such as experience, skills, documents, and links
Builds a knowledge base from that information
Uses AI to answer user queries accurately
Lives as a widget you can embed on modern websites
Lets you configure behavior through an admin portal
Integrates with Calendly for instant scheduling
Shares your hourly rates or availability when asked
Provides GitHub, LinkedIn, and portfolio links dynamically per request

Think of it as your digital representative who never sleeps, never forgets, and never asks for coffee breaks.

Personalization and Control

One of the biggest goals with Klyro is control. Not just over knowledge, but over personality and presentation.

Persona Based AI Bots

You can shape how the bot behaves:

Professional and formal
Casual and friendly
Humorous and witty
Minimal and direct

This allows the assistant to match your brand or audience. A recruiter might get professionalism, while a gaming portfolio might get humor.

Custom Chatbot Instructions

You can define rules like:

What to avoid saying
How to respond to pricing questions
How to handle unknown queries
Tone and style guidelines

Knowledge Boundaries

The bot only answers based on the documents and links you provide.

This reduces hallucinations and keeps responses accurate and controlled.

It does not pretend to know things outside your data.

Custom Look and Feel

Klyro is not just about intelligence. It is also about visual identity.

You can:

Customize chatbot colors
Adjust widget shape and position
Match your website branding
Control how the chat UI appears to visitors

A smart assistant with bad UI is like a sports car with square wheels.

Why Not Just Use a Generic Chatbot?

Generic bots are usually:

Too broad
Not personalized
Scripted or rule based
Painful to configure
Detached from your brand identity

Klyro is designed to be you specific or product specific.

It is not trying to answer the entire internet.

It is trying to answer your users with your voice.

Real Use Cases

Klyro is surprisingly flexible:

Developer portfolios
Startup landing pages
Freelancers sharing rates and booking links
Product support sites
Personal branding pages

Anywhere you would normally write an FAQ, you can instead let people ask anything.

Lessons While Building

A few things became very clear:

People love chatting more than clicking.
Simplicity in setup matters more than feature count.
Branding and widget feel are as important as AI accuracy.
Personality makes assistants feel human.
Control over knowledge prevents misinformation.

Also, naming things is still harder than building them.

Try It Yourself

Product Hunt: https://www.producthunt.com/products/klyro
Widget Demo Video: https://www.loom.com/share/0f6e5c4273be4550ad4dcbac9e28c102
NPM Package: https://www.npmjs.com/package/@klyro/widget

The project is currently free to use and open for experimentation.

You can interact with the live version and see how conversational interfaces change the way users explore information.

What’s Next

Planned directions include:

Voice interaction
Better analytics
Deeper integrations
Smarter context handling

The goal is simple.

Make websites feel less like documents and more like conversations.

If you have ever answered the same question too many times, you already understand why this exists!

DEV Community: Areef Syed