New: Ask RAI — describe a problem and get matching solutionsTry it ↗
SUITE Academy · by Grow with Rajesh

Learn to put AI to work

Ready-to-use prompts for every team. Copy one into your AI tool, or try it with RAI.

Finance

Cash, collections, closing the books and reporting.
All Finance prompts and use cases →
  • Chase overdue invoices politely

    Draft reminders that get paid without souring the relationship.
    See the prompt

    You are my accounts receivable assistant. Here is a list of overdue invoices with customer name, invoice number, amount and days overdue: [paste list]. Draft a short, polite reminder for each, firmer as the days overdue increase. Mention the invoice number and amount, offer to resend the invoice, and keep each under 80 words.

    Try with RAI →
  • Spot cash gaps in the next 13 weeks

    Turn expected receipts and payments into a weekly cash view.
    See the prompt

    Here are my opening cash balance, expected customer receipts and planned payments for the next 13 weeks: [paste data]. Build a week-by-week cash table with opening balance, inflows, outflows and closing balance. Highlight any week where cash goes below [minimum balance] and suggest three practical ways to cover the gap.

    Try with RAI →
  • Explain this month's numbers

    Get a plain-English summary of what changed and why.
    See the prompt

    Here are this month's and last month's profit and loss figures: [paste figures]. Explain the five biggest changes in plain English for a business owner, with the likely reasons and one question I should ask my team about each.

    Try with RAI →

HR

Hiring, onboarding, policies and people reviews.
All HR prompts and use cases →
  • Write a clear job description

    A JD that attracts the right people and filters the rest.
    See the prompt

    Write a job description for a [role] at a [type and size of company] in [city]. Include a two-line summary, what they'll do in the first 90 days, must-have and nice-to-have skills, and how we work. Keep it under 400 words and avoid jargon.

    Try with RAI →
  • Shortlist candidates against the role

    Compare CVs to the job description, fairly and quickly.
    See the prompt

    Here is the job description: [paste]. Here are summaries of the candidates' CVs: [paste]. Score each candidate from 1 to 5 against the must-have skills, give one line of reasoning per score, and list three interview questions for the top three. Base it only on skills and experience.

    Try with RAI →
  • Plan a new joiner's first week

    A day-by-day onboarding plan with owners.
    See the prompt

    A new [role] joins on [date]. Create a day-by-day plan for their first week: accounts and equipment to set up, people to meet, documents to read and one small task to complete. Add an owner for each item and a short welcome message from the manager.

    Try with RAI →

Marketing

Content, campaigns and finding out what works.
All Marketing prompts and use cases →
  • Write a LinkedIn post from a client win

    Turn one result into a short, credible post.
    See the prompt

    Here is a recent client result: [what we did, for what kind of client, and the outcome]. Write a LinkedIn post in a confident but humble tone: a strong first line, the problem, what we changed, the result and one lesson. Under 180 words, no hashtags in the body, three relevant hashtags at the end.

    Try with RAI →
  • Plan a month of posts

    A four-week calendar with themes and captions.
    See the prompt

    My business is [what we do] for [audience]. Create a four-week social media calendar for [channels] with three posts a week. For each post give the theme, a hook line, a short caption and a visual idea. Mix education, proof and offers.

    Try with RAI →
  • Write copy that follows our brand voice

    On-brand landing page, email or ad copy.
    See the prompt

    Here are our brand guidelines and two examples of our writing: [paste]. Write [landing page section / email / ad] copy for [offer] aimed at [audience]. Match our tone and vocabulary, keep sentences short, and give two headline options.

    Try with RAI →

Sales

Enquiries, follow-ups, proposals and the pipeline.
All Sales prompts and use cases →
  • Reply to a new enquiry fast

    A helpful first reply that moves to a call.
    See the prompt

    A prospect sent this enquiry: [paste]. Write a reply that thanks them, answers what we can, asks the two most important qualifying questions and proposes a short call with two time options. Friendly and under 120 words.

    Try with RAI →
  • Write a follow-up sequence

    Three follow-ups that don't sound pushy.
    See the prompt

    We sent a quotation for [what] to [type of client] on [date] and haven't heard back. Write three follow-up messages spaced [3, 7 and 14] days apart. Each should add something useful, such as an answer to a likely concern or a relevant example, and end with one clear question.

    Try with RAI →
  • Build a proposal outline

    Structure a proposal around the client's problem.
    See the prompt

    Client: [name and industry]. Their problem: [problem]. Our solution: [solution]. Create a proposal outline with an executive summary, their situation in their words, our approach, timeline, what's included, what's not included, and next steps. Leave pricing as a placeholder.

    Try with RAI →

Tech

Requests, documentation, incidents and internal tools.
All Tech prompts and use cases →
  • Turn a request into a clear spec

    From a vague ask to something buildable.
    See the prompt

    A team member asked for: [paste request]. Turn it into a short specification: the problem, who uses it, user stories, acceptance criteria, data needed, and open questions to confirm before building. Keep it to one page.

    Try with RAI →
  • Write documentation for a process

    Step-by-step docs your team will actually use.
    See the prompt

    Here are my rough notes on how we [process]: [paste]. Write clear documentation with a purpose line, prerequisites, numbered steps, screenshots to add, common mistakes and who to contact. Use simple language.

    Try with RAI →
  • Triage support tickets

    Group, prioritise and route the queue.
    See the prompt

    Here are this week's support tickets with subject and description: [paste]. Group them by category, rate each as urgent, normal or low with a reason, suggest which team should own each group, and list any repeating issue that needs a permanent fix.

    Try with RAI →