vs. Fine-Tuning vs. Raw API
"The most powerful person in the room is the one who can make the AI behave exactly the way they need it to."
Ethan Mollick, Co-Intelligence: Living and Working with AI - 2024
| Approach | What You're Doing | Skill Required | Best For |
|---|---|---|---|
| Raw API | Sending messages to a model directly | Coding required | Custom integrations |
| Fine-Tuning | Retraining the model weights on your data | ML expertise | Consistent style/domain knowledge |
| AI Assistant / Custom GPT | Wrapping a model with instructions + knowledge + tools | No code needed | Team tools, expert personas |
- A system prompt defining its persona and rules
- Knowledge files it can reference
- Tool actions it can perform (call APIs, search, execute code)
As the comparison between Custom GPTs and Claude Projects notes: all three platforms (OpenAI GPTs, Google Gems, Claude Projects) require no coding and can be built in under 10 minutes. (Stackviv, 2025)
The business case is compelling: you’re packaging the expertise of your best team members into a tool that any colleague can access at 3am.
Designing the System Prompt and Persona
The system prompt is the most important document you’ll write for your assistant. Think of it as the job description, operating procedures, and personality guide combined.
A weak system prompt
You are an HR assistant. Help employees with HR questions.
A strong system prompt
You are Aria, the HR assistant for AcmeCorp. Your role is to help
employees quickly find answers to HR policy questions, benefits
information, and leave procedures.
TONE: Professional but warm. Never bureaucratic. Use plain English.
RULES:
- Always cite the specific policy document and section you're referencing
- If you're unsure, say so clearly and direct the employee to [email protected]
- Never speculate about disciplinary matters — always escalate to HR
- Do not discuss compensation details for other employees
FORMAT: Keep responses under 200 words unless a complex explanation is needed.
START: Greet the user by name if provided. Ask how you can help.
Attaching Knowledge Files and Enabling Retrieval
This is where AI assistants go from chatbots to actual business tools.
You can upload PDFs, Word docs, spreadsheets, and plain text files. The assistant uses Retrieval-Augmented Generation (RAG) under the hood — it searches your documents and grounds its answers in your actual content rather than hallucinating.
What to upload for an HR assistant
- Employee handbook (PDF)
- Benefits guide
- Leave policy document
- Frequently asked questions doc (a curated one you write yourself — this dramatically improves accuracy)
- Org chart and contact directory
What makes retrieval work well
- Clean, well-structured documents with clear headings
- Avoid scanned PDFs with poor OCR — extract text first
- Break giant documents into topic-specific files; smaller files = more precise retrieval
- Include a "FAQ" document — anticipate the top 20 questions and write ideal answers
APIs Your Assistant Can Call
This is what separates a knowledge assistant from an action-taking assistant.
In OpenAI’s GPT Builder, you can add Actions — API calls the assistant can make in response to user requests. Claude Projects can now connect via MCP (Model Context Protocol).
Examples of useful actions
- Query your HR system: "How many leave days do I have left?"
- Look up a customer record in your CRM
- Create a Jira ticket from a bug report described in natural language
- Check real-time inventory before answering a product availability question
Sharing, Publishing, and Controlling Access
Custom GPTs (OpenAI)
- Private (only you)
- Link-sharing (anyone with the link)
- Public in GPT Store (discoverable by all ChatGPT users)
Claude Projects (Anthropic)
- Private to your account
- Shared within your Team/Enterprise workspace
- No public marketplace (by design — stronger data privacy)
Custom GPTs can be published to the GPT Store — other users can discover and use your creation. This makes them strong for external-facing tools. (Grokipedia, 2026)
My recommendation
Measuring Quality and Iterating Over Time
Claude Projects (Anthropic)
- Accuracy rate — spot-check 20 random responses weekly; mark each correct/incorrect/partially correct
- Escalation rate — what percentage of questions get "I'm not sure, contact HR"? Aim to reduce this by improving knowledge files
- User satisfaction — add a thumbs up/down to your wrapper UI if building a custom interface
- Coverage gaps — collect unanswered or poorly-answered questions as input for your next knowledge file update
Tools at a Glance
| Platform | Best For | Key Advantage |
|---|---|---|
| OpenAI GPT Builder | Public tools, code execution, image gen | GPT Store distribution |
| Claude Projects | Internal team tools, large documents | Privacy, 200K context window |
| Google Gems | Google Workspace integration | Live Drive syncing |
| Hugging Face Spaces | Open-source model deployment | Full customisation, free tier |
| Cohere Coral | Enterprise knowledge assistants | Strong enterprise compliance |
In 2027, the competitive advantage isn’t access to AI — everyone has that. It’s the ability to *configure* AI precisely for your team, your domain, and your customers. Building an AI assistant is how you turn a generic tool into an institutional asset. And you don’t need to write a single line of code to start.
Explore project snapshots or discuss custom web solutions.
The models are commoditising. The prompts, the personas, the knowledge bases — the configurations — that's where the moat is being built.
Thank You for Spending Your Valuable Time
I truly appreciate you taking the time to read blog. Your valuable time means a lot to me, and I hope you found the content insightful and engaging!
Frequently Asked Questions
Custom GPTs require ChatGPT Plus or higher. Claude Projects are available on Claude Free (with limits — max 5 projects, no RAG), and fully on Claude Pro and Team plans.
Two mechanisms: (1) make your knowledge files comprehensive enough that answers are always grounded in documents, and (2) add explicit instructions in the system prompt: "If you cannot find the answer in the provided documents, say so clearly and do not speculate."
Yes, via Actions (OpenAI) or MCP integrations (Claude). You'll need a simple API endpoint — even a Google Apps Script or Zapier webhook works for basic use cases.
A Custom GPT remembers your instructions, has access to your uploaded documents, and maintains its persona across every conversation. Regular ChatGPT starts fresh. The assistant is the configuration; the model is the engine.
For internal team tools and knowledge assistants, no-code is excellent — fast to build, easy to iterate, no maintenance overhead. For customer-facing products, complex multi-step workflows, or tight UI integration, you'll want the API.
Comments are closed