Start with a real operating story
Describe one customer joining, submitting incomplete proof, correcting it, receiving approval, and redeeming a reward. Ask the software to demonstrate each step, including the awkward cases.
Then describe the staff experience: who reviews, who fulfills, what happens when the owner is away, and how an exception is recorded. An attractive dashboard is useful only if the underlying process fits your business.
A requirements scorecard for Nanocreator World
This scorecard reflects the inspected campaign workflow. It separates functionality from work that still belongs to the business. It is not a claim that every deployment or communication integration is configured.
| Requirement | Current scope | What to check |
|---|---|---|
| Enrollment and invitations | Campaign links, QR sharing, Google participant sign-in | Can your customers complete the journey? |
| Evidence and review | Submitted HTTPS link or written details; owner review | Can staff assess your proposed action? |
| Reward fulfillment | Codes after approval; authorized staff redemption | Can your team fulfill the exact terms? |
| Recruitment sources | Counter, Instagram, email, partner, direct/unknown | Are links placed consistently? |
| Content reuse rights | Owner-managed permission process | Where will agreements and assets be recorded? |
| Social verification | Human review; no automatic Instagram verification claimed | Does your staffing plan cover review? |
| Sales attribution | No verified POS purchase attribution claimed | Do you need another system? |
| Messages, pricing, support | Confirm actual configuration and commercial offer | What is available for your account today? |
Score missing requirements before optional features
Mark each requirement essential, useful, or unnecessary for the next campaign. For each essential item, record demonstrated, manual workaround, or unresolved. An unresolved essential requirement should affect the decision more than several attractive extras.
For example, a business that must reward verified purchases needs transaction evidence. A proof-review tool is not automatically the right substitute. A business running a small customer-content pilot may care much more about understandable enrollment and staff redemption.
Ask about operating ownership
Confirm who can access customer records, how account changes are handled, and what support is available. Ask about data access or export requirements before relying on an assumed migration path. Do not treat a feature as available because it appears on a future roadmap.
Separate “the application has messaging code” from “our account is configured and permitted to send the message we want.” Deployment settings and communication permissions matter to the actual workflow.
A spreadsheet may still be enough
If one person runs a tiny pilot with little handoff risk, a carefully maintained sheet can help validate the process. Switch when missed decisions, duplicated records, reward confusion, or staff time justify the change.
Use the spreadsheet comparison guide to record current effort. Evaluate the complete cost of software plus remaining manual work; no tool removes the need to design an honest offer and fulfill the customer promise.
Try the workflow you are evaluating.
Open a workspace to set up a campaign, then check it against your essential requirements.
Open your workspacePlanning your spend? Use the reward-budget calculator. Ready to see the product? Walk through the campaign flow.