Chat assistants

ChatGPT: a general assistant that is good at drafts

What ChatGPT is good at, where it quietly fails, and how to write a prompt that gets a usable first draft.

  • Admin
  • 3 min read

Pricing

Free tier; paid plans from about US$20/month (check the official page)

Official site

Open the official website (opens in a new tab)

Prices and plans change. Check the official page before you pay.

ChatGPT is the assistant most people meet first. It is a text interface to a large language model, and its strength is producing a plausible first draft of almost anything: an email, an explanation, a small script, a plan.

What it is good at

  • Explaining a concept at the level you ask for. "Explain database indexes to someone who knows Python but not SQL" produces something more useful than a textbook paragraph.
  • Rewriting text. Shortening, changing tone, fixing grammar, turning bullet points into prose.
  • First drafts of structured work. An outline, a checklist, a lesson plan, a commit message.
  • Small code tasks. A function, a regex, a test case, an explanation of an error message.

The common thread is that you can judge the output quickly. If you can tell a good answer from a bad one, the assistant saves time. If you cannot, it is a confident source of mistakes.

Where it fails

It invents facts, citations and API details with the same tone it uses for correct ones. It does not know what happened after its training cutoff, and it will not reliably tell you that it does not know. Long chains of arithmetic, precise dates and niche library specifics are the usual failure points.

The practical rule: use it to draft, then verify anything that would be embarrassing to get wrong. Treat every factual claim as a lead, not a conclusion.

Writing a prompt that works

A good prompt has four parts:

  1. Role and goal. "You are a technical editor. My goal is a 150-word summary for a changelog."
  2. Context. Who reads it, what they already know, what has been tried.
  3. Constraints. Length, tone, format, what to avoid.
  4. An example. One line of the style you want is worth a paragraph of description.

Iterate rather than perfecting the first prompt. "Shorter, less formal, keep the numbers" is a normal follow-up and usually faster than a rewrite.

Pricing and plans

There is a free tier with limits and paid plans from around US$20 per month, with higher tiers for heavier use. Features and model names change often, so check the official pricing page before committing.

Using it well

  • Keep a document of prompts that worked; they are reusable assets.
  • Ask for the reasoning before the answer when the topic is hard, then check the reasoning.
  • Paste the actual error, not a summary of it.
  • Never paste secrets, customer data or unreleased code into a consumer chat unless your organisation has approved that use.

Who it is for

Beginners learning a topic, writers producing drafts, developers debugging small problems, and anyone who needs a fast second opinion. It is not a substitute for a database, a lawyer or a doctor, and it should not be the only reviewer of anything important.

Alternatives

Claude and Gemini are close competitors with different strengths: Claude tends to be careful with long documents, Gemini is tied into Google’s tools. For coding specifically, Copilot and Cursor put a model inside the editor, which changes the workflow more than the model does.

Admin

About the author

Admin

Instructor and technical writer at tutorials.in

Writes beginner lessons for tutorials.in. Each lesson is checked against the language or tool documentation, and examples are run before publishing.

Reviewed by the editorial team before publishing. Last updated November 16, 2026.