> For the complete documentation index, see [llms.txt](https://docs.superagency.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superagency.pro/aisa-founder-compensation-adjustment-memo.md). # AISA – Founder Compensation Adjustment Memo Date: April 27, 2026\ Effective From: May 1, 2026 *** #### Summary This memo records a minor adjustment to founder compensation during AISA’s current lean execution phase (Q2–Q3 2026). * Previous stipend: USD $1,000/month (approx., variable) * Updated stipend: €300 per week * Currency: EUR (primary disbursement currency) *** #### Rationale This adjustment reflects the transition into a critical full-time execution phase, focused on: * Securing pilot projects and Letters of Intent (LOIs) * Delivering early AICitySim simulation work * Advancing fundraising efforts for the current round The team is currently operating in a lean configuration (Founder + Engineering + DevOps support), with reduced burn relative to prior plans. The updated stipend: * Remains materially below market rate for a full-time founder/operator * Supports sustainable day-to-day living during an intensive execution period * Reduces operational friction and distraction during a results-driven phase Currency Note:\ The stipend is denominated in EUR to optimise treasury management, reduce FX conversion costs, and better align with current currency reserves (EUR/AUD), given limited USD liquidity and ongoing macroeconomic volatility. *** #### Treasury Context * Approximate treasury position as of date of memo: \~SGD 30,000 * Current structure allows this adjustment without materially impacting runway * Continued emphasis remains on lean operations and disciplined capital deployment *** #### Forward Adjustment Framework The current stipend level is intended to remain in place until clear, sustained traction is achieved. Founder compensation may be reviewed upon one or more of the following conditions: * Consistent pilot volume: e.g. \~2+ paid simulation projects per month * Sustained revenue: e.g. \~$5,000–$10,000+ Monthly Recurring Revenue (MRR) * Funding close: completion of a funding round of ≥ $100,000 Any future adjustment would likely move toward a $400–$500/week equivalent range, subject to treasury position and growth priorities at that time. *** #### Discipline & Contingency This adjustment reflects a defined execution window through 2026. In the absence of meaningful traction (revenue, pilots, or funding) by year-end: * Founder compensation and overall operating model will be reassessed alongside broader company viability and direction *** #### Closing Note This adjustment is designed to balance: * Founder sustainability * Capital discipline * Execution focus while maintaining strong alignment with AISA’s near-term objective: Demonstrating real-world traction sufficient to unlock the next phase of growth. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.superagency.pro/aisa-founder-compensation-adjustment-memo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.