Build a sponsorship-tracking CRM from a spreadsheet
Source sponsored by Manus. This source was published by No Code MBA and sponsored by Manus. The article includes a Manus referral link. Agents on the Job is not sponsored by Manus.
Turn a sponsorship spreadsheet into a simple internal CRM app with a drag-and-drop status board.
What the agent did
Source-reported example · as described by No Code MBA (channel host, name not stated)
The No Code MBA channel host asked Manus to replace a Google spreadsheet with a CRM web app for YouTube sponsorship requests. Manus built a full-stack app with a database; follow-up requests added 10 sample rows, publish dates, status tracking and a Trello-style board with a table view.
The author reports a seven-stage board (negotiating to completed) whose drag-and-drop "worked flawlessly", and calls it "production-ready".
Limitations
It was tried with sample data; the article doesn't report ongoing real use. The author says the builder suits MVPs and internal tools, and complex logic or integrations may need traditional development.
Try it in your business
What you'll need
A Manus account (credits; app building uses more). The exact prompts, hosting after the build and whether real data was moved over are not disclosed.
Built entirely from plain-language requests inside Manus; no code written or apps connected by the author.
Starting prompt
The author didn't publish their prompt (checked the full article text and FAQ; the paraphrased request is described, not quoted; linked YouTube video not inspected), so this is our adaptation.
How ours differs from the original setup: Written for Manus like the author; combines his initial request and follow-ups into one prompt; adds a payment stage and a review-before-real-data step.
Build me a simple internal web app to track sponsorship deals, replacing my spreadsheet. Fields: sponsor name, contact, deal amount, payment status, deliverable, publish date and status. Use these status stages: [your stages, e.g. negotiating, confirmed, in production, scheduled, published, paid]. Give me a board view with drag-and-drop between stages and a table view. Start with 10 sample rows so I can test it. Don't import my real data or connect any accounts until I've reviewed it.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Onboard a new client end to end: draft the contract, set up their Slack channel and podcast feed, and build website mockups for your review
Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude with skills (or saved instructions) describing your onboarding process; your internal docs, past contracts and the client's correspondence; access to your documents (for example Google Drive and Docs) and, if you let it do setup steps, to your team chat (the author used Slack via Claude's browser use) and client database; your own review of the contract, every account, channel or access change, and every client message. Building the skills was a one-off investment of about a day of the author's time, by his estimate.
Help me onboard a new client for my [type of service] business. Work in stages and stop for my approval at the end of each one. Stage 0 (first time only): Read my internal docs and past client notes in [folder]. Write a short overview of what my business does and how it works, then draft a step-by-step client onboarding checklist. I'll correct it. Once I approve it, save it as reusable instructions I can run for future clients. Stage 1, contract: Using the client emails and call notes I've attached and my past contracts in [folder], draft a service contract for [client] as a document. Look up their public details (legal name, registered address, registration number) and list where you found each one. Highlight anything that differs from my usual contract or that you're unsure about. Don't send it or upload it to a signing service. I'll review it and send it myself. Stage 2, setup: List every channel, record and account this client needs (for example a shared [Slack] channel that follows my naming pattern, or an entry in my client database), and wait for my OK before you create each one. Don't invite the client, grant access, change permissions, or enter any password or payment details. Give me the invite link or the exact page to open, and I'll do those steps. Stage 3, tailoring and samples: Review [the client's website or materials], list the special cases my service needs to handle for them, and propose a rule for each. After I approve the rules, prepare [sample deliverables] for me to check, and flag anything you're unsure about. Stage 4, mockups and delivery setup: Make mockups of [how my deliverable would look on their website], using their public branding, and draft [the feed, page or other delivery setup] privately. Don't publish anything until I approve it. Stage 5, client update: Don't write or send messages to the client. Give me a bullet list of points to cover in my update, then check my draft for clarity and for anything I've missed. Finish with a checklist of what's done, what's waiting for my approval, and what I need to do myself.
Project inventory and recommend when to reorder each product
Have Claude Code pull inventory and sales data, project the next twelve months of sales and stock by product, and recommend when to reorder each one, using written notes on supplier lead times and holidays.
Author's example instructions
You'll need: Claude Code; sales and inventory data by SKU (the author pulled it from Amazon with scripts Claude Code wrote); written notes per brand covering supplier lead times, holiday closures, off-platform stock and past stockouts; an instruction file or command listing the projection steps. Not disclosed: The scripts' code and how the Amazon credentials were connected; the full text of the instruction file and per-brand context files; the number of brands and SKUs; how accurate the projections turned out against actual sales.
1. Check to see if the sales/inventory data we have locally is >5 days old, and if not, pull fresh data from Amazon. 2. Check the context notes for the brand it's working on. 3. Pull inventory and sales data from the local cache. 4. Display the trailing twelve month sales data by SKU and by month. 5. Describe any factors it's going to use to make adjustments to TTM sales data when projecting NTM sales. 6. Review its stated adjustment factors, then project NTM sales by SKU on a monthly basis, and display the amount of stock remaining at the end of each month based on those projections. Use Python for the math here. 7. Recommend when to reorder each SKU, factoring in CNY and other holidays.
Build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive
Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your QuickBooks, email and OneDrive (the post does not say how it was connected); the estimate and job-cost categories your current software uses, ideally with a sample from one job; your own review of the tracker and of anything the bots prepare.
I want an estimate and job-cost tracker to replace [current software or spreadsheet]. Build it as a workbook saved in [OneDrive folder] with: an estimate sheet per job ([line items and cost codes]), a bills and actual-cost sheet per job, and a summary of budget against actual cost per job. Fill the cost data from QuickBooks ([company file]) and from bill emails in [mailbox or label], read-only: do not change anything in QuickBooks, send any email or delete anything. Match each bill to a job and cost code, and list the ones you cannot match, with the reason. First show me the structure and a sample for [one job] before you fill in the rest. For draws: when I ask, prepare the draw package for [job], draw number [n], using only invoices that were not in earlier draws, and list any issues from the last draw request. Save it as a draft and write a draft email to [bank contact]. Do not send anything to the bank; show me the package and the draft first.

