Running apps on your own means there are days when you spend more time on everything around the code than on the code itself. User support emails, store policy updates, ad revenue reports. Work that a company would split across departments all lands on one desk — yours.
I started weaving Gemini into the business side of my work when I realized this administrative layer was quietly eating the hours I wanted to spend building. Operating several wallpaper apps in parallel, the paperwork never shrinks; it grows a little every year. What follows is an honest account of the uses that stuck, and the ones I tried and let go.
Support email drafts were the first thing that actually paid off
The biggest time sink was responding to inquiries in English from users around the world. Even when the content was simple, composing a polite, well-formed reply used to take me a good fifteen minutes each time.
Since handing the first draft to Gemini, my prompt looks something like this:
Write a reply in English to the user inquiry below.
- Tone: polite but not stiff
- Message: the wallpaper display bug they reported will be fixed in the next update
- Include: thanks for the report, rough timing (within next week)
- Do NOT include: excessive apologies, technical internals
The part that matters most is the "do not include" line. Without it, the draft drifts toward the boilerplate of English support emails — long and over-apologetic. I never send a draft untouched: anything that constitutes a promise, like a fix date, gets verified by me before it goes out. Commitments should come from a person, not from a model. That is a line I want to keep.
For policy updates, ask for the diff and the impact — not a summary
Policy update notices from app stores and ad platforms are the documents I used to postpone reading, and I once nearly missed an important change by skimming.
Now I hand Gemini the document and ask for differences and consequences rather than a summary:
Read this policy update and organize it from these angles:
1. What has substantively changed from the previous version
2. Which parts affect an operator of wallpaper/image apps
3. If action is required, the deadline
Ask for a plain summary and you get generalities that apply to everyone. Reframing the question as "what changes for my app" turned the output into something I can use directly as a task list. I have found this holds for almost every summarization job: give it your vantage point, or it will give you nobody's.
In report analysis, ask which numbers to look at — not for the totals
I also lean on Gemini for revenue reports. When reviewing monthly AdMob data, I used to eyeball eCPM and impression swings and guess at causes. Now I provide the data and ask:
"Based on this data, what combinations of factors could explain the revenue drop compared to last month?"
What comes back is hypothesis, not verdict — but that is exactly the value. It surfaces angles outside my own assumptions: an eCPM dip in one country, an impression decline in one ad format. Inside Google Sheets, having it build complex VLOOKUP or pivot formulas from natural language has also been reliably useful.
The one rule I keep: never let Gemini's output be the final word on an aggregate figure. Sums and ratios occasionally drift, so the definitive numbers always come from spreadsheet formulas I can audit. Delegate the hypotheses, keep the verification. That division of labor is what works for me.
Slides and meeting notes? Honestly, I barely use them
Business-use articles love to showcase slide generation and meeting summaries, but in my working life they almost never come up. A one-person studio has no weekly deck and no meeting minutes.
That is a statement about my business shape, not about the features. If your team runs recurring status reports, drafting fixed-format documents is exactly where this saves time. A tool's value is decided not by its feature list but by where it lands in your particular workflow — that was my takeaway from trying and discarding these.
The biggest free-vs-Workspace difference is how your data is handled
Before comparing features, the question worth answering for business use is what happens to the data you type in. Gemini delivered through Google Workspace is designed so that your inputs are not used to train the models, and it operates within your organization's data governance. That is the fundamental difference from the free consumer setup.
My own split: anything touching user email addresses or support threads stays inside the Workspace environment; general research happens in my personal one. Plan structures and pricing keep changing, so rather than copying a table here that will age badly, I would point you to the official Google Workspace pricing page for current terms.
Recurring instructions belong in Gems — build a shelf of tools
Once the habits settled, I noticed I was retyping the same preamble every time: "as the operator of wallpaper apps," "polite but not stiff," and so on. The preamble itself had become a small chore.
Gemini's Gems let you save instructions and context as reusable assistants. I keep three: support replies, policy reading, and report analysis. The support-reply Gem, for instance, carries the app overview, the tone rules, and a list of things never to promise (such as firm release dates).
With that in place, each use is just pasting in the inquiry text. Moving prompt craft from "something I reconstruct on the spot" to "something sitting on a shelf" turned out to be the single biggest time saving. If you have two or more instructions you repeat weekly, they probably deserve to be Gems.
What I delegate, and what I deliberately don't
After a few years of this, the line settled somewhere simple. Drafts, digests, hypotheses — work I can correct afterward — I delegate freely. Promises to users, finalized figures, the last call on how to interpret a policy — work whose mistakes land on someone other than me — I keep in my own hands, even when it is slower.
Efficiency talk usually centers on delegating more. In practice, deciding what not to delegate first is what made me comfortable delegating at all. That is the answer I have arrived at running this business alone.
Start small: pick one email you have been avoiding in your inbox and have Gemini draft the reply. Grow from wherever that experiment fits your own work. If you are carrying a one-person workload like mine, I hope these notes save you a few of those fifteen-minute detours.