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.
What the agent did
Source-reported example · as described by Pawan (@puvsandhu), owner of several companies; X bio: "Real estate. Property development. Construction." (surname not stated publicly)
The author, Pawan (@puvsandhu; X bio: "Real estate. Property development. Construction."), posted on X that he used to pay around $1,700 a month for construction-management software, which he mainly used for estimating, bills and job-cost tracking, plus a decent amount for warranty items; he says he barely touched its scheduling and task tools.
He says that after he started using Grok Bot it was "so simple to set up": he had Grok give him prompts to build a bot "staff" for each company he runs, then asked it to log into his accounts, update things, give him summaries and present the data.
When he saw how good the bots were at building tables and spreadsheets, and because his bookkeeper was entering every bill twice (once in QuickBooks and once in the construction software), he asked the bots to build the estimate and job-cost tracker the software had, connected directly to QuickBooks, email and OneDrive.
He says it "worked really well" and that a couple of days later he cancelled the subscription. He now asks the bots for summaries or has them update the dashboards for a quick review, and opens the workbooks when he wants to go deeper.
For draw requests, he says he asks the bots to put the package together and email it to the bank; he says they know not to include invoices from previous draws and flag any issues from the last request.
The post does not name the software he replaced, show the tracker, give a prompt, or say whether he reads the draw package or the email before it goes to the bank.
He says he cancelled the subscription (about $1,700 a month) a couple of days after the bots built the tracker, and that this puts $20K a year back in his pocket (his own figure; he does not say how it was calculated).
Limitations
Single X post, the author's own account. The software he replaced is not named, and the post does not show the tracker, its structure, any numbers from it, or a prompt. The $20K a year and "worked really well" are his own statements.
For draw requests the post says the bots put the package together and email it to the bank; it does not say whether he reviews the package or the email first.
(In a different post from 2026-10-28 he writes that his agents can write any email but nothing goes out until he hits Send; that is a general statement in another post, so this listing does not apply it to draw packages.)
The post gives no count of his companies (that other post says both 3 businesses and 4 companies, so no count is stated here). The model is not stated, and the post does not say how setup went beyond "a couple of days" before he cancelled.
Try it in your business
What 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.
The post says the tracker is connected directly to QuickBooks, email and OneDrive. How the connections were made is not described.
Starting prompt
The author didn't publish their prompt (read the full note_tweet text of the post; no prompt or instruction is quoted), so this is our adaptation.
How ours differs from the original setup: Same execution agent (Grok Bot). The author published no prompt, so this is our starting prompt built from his description of the tracker, its three connections and the draw-request step. Job names, cost codes, folders and the software being replaced are blanks for you to fill in.
It adds read-only access to QuickBooks, a sample-first step and an explicit draft-only instruction for the bank email, because the post says the bots email the package to the bank and does not say whether he reviews it first.
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.
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
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.
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.
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.

