This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
What I Built
I built ReplyCraft AI, a local-first AI customer communication assistant designed for freelancers, small businesses, and independent service providers.
Small businesses often spend valuable time answering repetitive customer questions, drafting emails, and explaining their services. ReplyCraft explores how AI can help reduce this repetitive work.
The project includes three main features:
- AI Reply Generator: Generates customer-service replies in professional, friendly, firm, and apologetic tones.
- Business-Specific Chatbot: Answers customer questions using information about a business, such as its services, opening hours, and policies.
- Website Chat Widget: An embeddable JavaScript chat interface that lets website visitors interact with the chatbot.
I demonstrated the widget using a sample repair business called QuickFix Repairs.
The potential customers are repair shops, freelancers, local service providers, and small businesses that want a basic AI-assisted customer support experience without relying on a paid hosted AI API for every request.
A potential future business model could include paid setup and customization, optional maintenance, or a hosted version for businesses. These are ideas to validate with real users; I have not yet established paying customers.
Demo
🎥 Watch the ReplyCraft AI Demo on YouTube
The video demonstrates the dashboard, AI reply generator, chatbot, and website chat widget.
Code
💻 View the ReplyCraft AI GitHub Repository
The project is built with Python, FastAPI, React, TypeScript, Vite, and Ollama.
How I Built It
I built ReplyCraft AI with a React and TypeScript frontend and a Python backend powered by FastAPI. The backend exposes API endpoints for generating customer replies and handling chatbot conversations.
For local AI inference, I used Ollama with open-weight language models, including Qwen 2.5 (1.5B) and Llama 3.2 (3B) during development.
The application sends user prompts and business-specific context to the backend, which communicates with the locally running Ollama service to generate responses.
I chose this architecture to experiment with AI-powered customer communication without making a paid external model API a core requirement.
The main development challenges included connecting the frontend and backend, generating replies in different tones, providing relevant business context to the chatbot, and connecting a standalone JavaScript widget to the API.
The current project is a working local prototype. Persistent settings, stronger security controls, and production deployment are future improvements.
Why Does Open Innovation Matter?
Open innovation matters because it gives developers more flexibility to experiment, build, and adapt technology to real-world problems.
Using open-weight models through Ollama allowed me to experiment with different models locally instead of depending entirely on a proprietary hosted AI API. This made it possible to explore local inference, compare model options, and build a practical prototype without per-request charges from a hosted model provider.
Local inference can also help keep prompts on a user's machine when the application is configured to operate locally. However, privacy depends on the complete system configuration, and local inference still has hardware, electricity, and maintenance costs.
Open-weight models are not automatically unrestricted or identical to fully open-source software; their licenses and usage terms still matter.
For ReplyCraft, the most important benefit is control and flexibility. I can experiment with different models and improve the application around the needs of small businesses without tying the entire project to one paid AI API.
Open-source tools such as FastAPI and React also made it possible to build the application using accessible development technologies.
This project showed me that building a useful AI application is not only about generating text. The user experience, business context, reliability, privacy, and deployment decisions are equally important.
Prize Categories
ReplyCraft AI focuses on local inference and open-weight language models. I would only select partner prize categories for which the project meets the official eligibility criteria.
What's Next?
My next goals for ReplyCraft AI are:
- Persist business settings and reply history.
- Improve how the chatbot handles questions it cannot confidently answer.
- Strengthen security before exposing the backend beyond local development.
- Make the website widget easier to configure.
- Gather feedback from small business owners and validate which features they would actually pay for.
I'm excited to keep improving the project and explore how open-weight AI can make useful tools more accessible to small businesses.
I'd love to hear your feedback: What feature would make an AI customer support assistant genuinely useful for a small business?
Thanks for reading, and happy Hacktoberfest! 🚀
Top comments (0)