Sundai workshop: engineering and business loops

Use this path for Sundai’s Engineering Business Loops with Egbe workshop and for the work you continue afterward. The aim is to connect action, measurement and adaptation so a demo becomes a starting point for the next useful decision.

The Sundai Hack 149 event page has the event logistics. It also mentions free Egbe credits. Confirm your available credit and account limits before authorizing paid work.

Bring a question you can move forward

Bring an idea, an existing product or a specific customer problem. Useful starting points include a first product result, a broken customer journey or an uncertainty about who would choose the offer. Existing code, customer notes and prior experiments help your agent continue from real context.

Connect through Quickstart and Connect your agent. Check the capabilities available to your project before choosing work that depends on them.

Help me choose a useful workshop outcome for this idea or product. Review what I already have. Propose a result we can complete and verify, explain the business question it addresses, and identify what would remain uncertain afterward. Prepare any research or acquisition materials for review; ask before paid work, outreach or publication.

Expect one recommended focus with a reason, a credible alternative, the agent’s deliverable and any decision or input needed from you.

Connect business judgment to engineering

Use the Business Loop to choose what deserves attention. Use the engineering loop when the agreed work requires a product change. If the important uncertainty concerns customer demand or reach, the acquisition guide helps shape a bounded test.

For an illustrative lesson-planning product, you might build one complete path from a tutor’s input to useful materials and verify the output on meaningful examples. Separately, you might prepare a customer test to learn whether that result matters to the intended audience. A working demonstration establishes the behavior you verified; demand remains a question for customer evidence.

Choose the order from the uncertainty and dependencies in your project. A workshop does not require every capability or a paid campaign.

Make the demo a useful handoff

Show the intended customer result, what actually works, the evidence you inspected and the main remaining uncertainty. Explain the next action and when its effect could be assessed. Keep prepared materials, approved actions and completed execution clearly distinguished.

Before you leave, preserve the plan, decisions and last verified result. Follow Continuity between sessions to resume manually or agree a recurring review. A scheduled loop needs your agreement and an available runner; a local runtime must remain awake and able to execute.

The practical outcome is work you can continue: a concrete result, evidence with honest limits and a next decision connected to your business goal.