Build and run a software business with Muse

To build and run a software business with Muse, connect Muse to NanoCorp, give the business's agents a focused product brief, and inspect the working customer journey before promoting it. After launch, use Muse to ask about usage, payments, customer questions, and the next change worth making.

NanoCorp supplies the business agents and tools. Your conversation with Meta's Muse is where you direct their work and receive their answers. You decide the customer, promise, and next investment. The connector behavior in this guide was checked against NanoCorp's assistant documentation on September 30, 2026.

This guide covers that build-and-operate cycle. For choosing an idea, read How to start a business with Muse. For connection instructions, use How to connect NanoCorp to Muse.

Scope a product someone can finish using

Your first deliverable should complete one useful customer job. Describe the starting input, the result, and the actions connecting them.

Consider a hypothetical tool for freelance photographers: the customer enters a shoot date and location, selects a supplied checklist, and saves a personal preparation plan. This is an example, not a customer story or a tested NanoCorp business.

The initial scope might include editing and saving that plan. Team accounts, calendar connections, automatic reminders, and a marketplace can wait. Each adds another workflow to check.

Give the agents a brief they can act on:

Ask my photography-planner business to build the first version around one job: create and save a preparation plan for an upcoming shoot. The customer enters a date and location, chooses a checklist, edits it, and returns to the saved plan. Keep calendar connections, team accounts, and reminders out of this version. Record the scope and acceptance checks in the business documents. Tell me what is built, what is missing, and what needs my input, with links to inspect the result.

If a proposed feature depends on another service, ask whether the connection exists and what setup it requires. A feature mentioned in a brief is not evidence that it is available.

Turn the brief into acceptance checks

Acceptance checks describe what must work to deliver the promise. Review the output without reading the code.

For the hypothetical planner, check these paths:

Customer action	Evidence to inspect
Open the product on a phone	Readable form and usable controls
Enter a shoot and choose a checklist	The correct preparation items appear
Edit and save the plan	The saved version retains the changes
Return later	The same plan can be opened again
Submit an incomplete form	A useful explanation of what to fix
Ask for help	A visible, working contact route

If customers have accounts, also check that one customer cannot view another customer's saved plans. Ask the agents which checks they ran, which failed, and which you need to try yourself. Open the supplied site link and follow the journey with sample information.

Judge the working page and saved result. Record specific failures, such as “the edited checklist disappears after reopening the plan.”

Review the first purchase and delivery together

Inspect the offer, payment, and access to the promised result together.

NanoCorp has tools for products, payment links, and customer subscriptions, but the product still needs the appropriate purchase and access flow. A monthly plan has a different setup from a one-off product. Ask the business agent to explain the chosen flow and any unfinished connection. See NanoCorp's subscription guide.

Use a review prompt like this:

Review the planner's first customer journey from landing page to saved plan. Explain what is free, what requires payment, and how a paying customer gets access. Give me the appropriate test payment route and steps I should try in my own browser. List failed or untested checks separately. Check that the public purchase route uses live checkout and that the page promises only features currently available.

Follow Testing your checkout for the test route. Test purchases do not move real money or count as revenue. Completing a checkout test also does not establish that delivery works: return to the product and verify the promised access or result.

Run one focused piece of work at a time

Muse can send a message to a NanoCorp business's agent, follow its work, relay questions, and bring back the answer. Each business processes one message at a time. Finish or stop the current turn before sending the next instruction.

Turns use credits and take variable time. Closing the conversation does not stop an active turn. Ask Muse to stop the turn if you need it stopped. Pausing a business prevents scheduled work; it does not stop an active turn, and messages can still start work. These behaviors are documented in Connect an AI assistant.

Check the account's credit balance before requesting a larger change. Review current NanoCorp plans and credits when planning recurring work. An instruction such as “ask me before changing the offer” communicates your preference; it is not a platform-enforced approval rule or spending limit.

Establish a cadence based on evidence

Start each review with customer problems and the current product. Look at incoming questions, failed journeys, real purchases, and whether people complete the useful action. Then choose one change and keep a record of why you chose it.

For the planner, a useful custom event could represent a successfully saved plan. Ask the agent whether that event is implemented and reporting before treating it as a metric. Pageviews alone do not tell you that the customer's task succeeded.

Try this operating prompt:

Review this business for the last seven complete days. Report visitors, successfully saved plans if that event exists, real payments, and unresolved customer questions. State the dates and sources. Separate known founder tests and test purchases where identifiable, and explain anything you cannot distinguish. Recommend one next task, connect it to the evidence, and record it in the task list.

Request these reviews yourself. The cadence does not mean Muse automatically initiates them. Inspect NanoCorp's dashboard alongside the answers.

Keep testing separate from demand

A founder repeatedly opening the site can generate activity. A test payment confirms part of a purchase flow. Neither shows that an independent customer wants the product.

When reading a report, check its dates, units, and exclusions. Are “payments” real transactions? Does “usage” mean visits or completed plans? Can founder testing be identified? If the available data cannot answer a question, keep that limitation beside the number.

Ask willing early users to try the workflow and describe where they became confused. Fix a demonstrated obstacle before expanding the product. For a broader view of product-building approaches, read Launch a SaaS without coding.

FAQ

Can Muse build my software business through NanoCorp?

A connected Muse assistant can direct NanoCorp's business agents and use their tools. Ask for a specific deliverable and inspect the result. The scope and any outside integrations determine what setup and review the product needs.

Do I need to know how to code?

You can give instructions in ordinary language. You still need to describe the customer job, try the product, and judge whether it fulfills the promise. Complex or sensitive workflows may need specialist review.

Does closing Muse stop the business's work?

No. An active agent turn continues and uses credits after the conversation closes. Ask Muse to stop the turn when needed. Pausing scheduled work is a separate action.

How do I know whether the business has real customers?

Inspect real payment records and relevant product activity for a stated period. Exclude test purchases, and identify founder testing where possible. Ask customers what they used and why. A successful test or a visitor count alone does not demonstrate demand.

Start with one useful workflow

To begin, connect NanoCorp to Muse and ask it to list your businesses. Choose the business you want to work on, then send a brief for one customer job and the checks that will show it works.