Stressor analysis

Why did I decide to do my Arch Stream in English when the project is in Swedish, Swedish is my native language, all my colleagues and the client is Swedish, and Barry, tho not Swedish, is fluent? Oh well, practicing my English is also useful I guess.

I’ve been thinking about some stressors, and figured I’d list them here.

• AI changes the SEO business
• The client runs out of money before we have a working product
• Google changes the search algorithm
• A competitor beats us to the market
• The company is acquired
• The business models shifts from a monthly, all-inclusive, subscription. Predictable variants include modular pricing or pricing based on clients/sites/reports/retention etc. Or a combination
• An investor demands that we “sprinkle a little AI” on the solution
• New regulations require client data to be stored in specific regions
• New tariffs make Azure hosting (currently selected platform) too expensive
• There’s a white label deal
• The dollar crashes
• It’s pretty obvious we need some sort of integration with book keeping, be it financial reports or API. Either we manage clients and payments, and report to the book keeping, or the book keeping reports to us. We don’t know this, and it is also subject to change.
• Based on the above, the client decides that payments will be handled within the service or
• The client decides that payments will be handled outside the service
• Word spreads and the sales skyrocket
• DDos attacks
• Hackers gain access to the database
• There’s a major power outage
• Clients demand feature to set permissions to users, or even groups of users

I’ll need a couple of more walks before returning to this list.