Roles & Theory
Learn how Swotmaker works, what each AI role does, and how SWOT/TOWS theory is translated into practical project outputs.
How to use the portal
Understand the project workflowStart by choosing the project category that best describes your situation: general strategy, HR situation, personal analysis, or idea analysis.
Then describe the context as clearly as possible. The context is the most important input because it guides the AI agents and the system algorithm.
No. You can enter your own strengths, weaknesses, opportunities, and threats if you already have them, but the initial SWOT matrix can also be skipped.
If the draft matrix is skipped, the Context Enrichment AI Agent can still use your situation description to prepare a structured SWOT draft.
The project moves through context definition, optional SWOT draft, AI enrichment, optional prioritization, Analyst AI relation mapping, Human in the loop review, system strategy calculation, and Strategy AI action planning.
The project timeline and checkpoints show which steps are finished, skipped, in progress, or still waiting.
Priorities become weights used later by the system algorithm. The first factor receives the strongest weight, the second receives a medium weight, and the remaining factors receive a base weight.
This makes the user input visible in the final strategy calculation instead of treating all SWOT factors as equally important.
AI interaction
How agents support the analysisThe portal uses three AI roles: Context Enrichment AI Agent, Analyst AI Agent, and Strategy AI Agent.
Each agent has a separate task, and the user decides when to run the next AI-assisted step.
It reads the original project context and prepares a clearer professional situation description together with a structured SWOT draft.
The agent should answer in the dominant language of the original user-provided context, regardless of the interface language.
It checks whether specific pairs of SWOT and TOWS factors have a real, project-specific relationship.
The agent proposes relation values, but the user can review the relation map before the strategy is calculated.
It receives the project context, SWOT factors, reviewed relations, and the recommended strategy calculated by the system algorithm.
Its role is to prepare a practical action plan, not to recalculate the strategy.
No. AI output is analytical support. It may contain mistakes, omissions, or interpretations that require human review.
The service should not be treated as legal, financial, medical, recruitment, investment, or other professional advice.
Rights and terms
Copyright and responsible useThe user is responsible for the information entered into the service, including project descriptions, SWOT factors, and any sensitive or confidential content.
Users should not enter information they are not allowed to process or share.
You may use your project outputs for your own analytical, educational, organizational, or business purposes.
You remain responsible for checking whether the generated output is accurate, appropriate, and safe to use in your context.
The service interface, logo, workflow design, system algorithm, naming, and explanatory service content are elements of the portal.
They should not be copied, resold, automatically scraped, or used to build a competing solution without permission from the creator.
No. PayPal donations are voluntary gifts supporting further development of the portal.
A donation does not unlock paid functionality, extend access, or create a subscription unless the service explicitly states otherwise.
The service may limit the number of analyses that can be created by a standard user, for example to one analysis per month.
Master users may have different limits for administration, testing, or development purposes.
SWOT and TOWS
Theory, outputs, and what the system deliversSWOT organizes a situation into strengths, weaknesses, opportunities, and threats.
It helps separate internal factors from external conditions and gives the project a clear strategic structure.
You receive a clearer professional situation description and a structured SWOT matrix prepared from your original context.
The result is designed to be readable before the next step, so you can understand the factors that will be used by Analyst AI Agent.
| Output | Shape in the project view | Why it matters |
|---|---|---|
| Professional situation description | Readable narrative section | Gives all later agents the same project context. |
| SWOT matrix | Four static lists: strengths, weaknesses, opportunities, threats | Turns the situation into structured analytical factors. |
| Project language | Response language follows the original context | Keeps outputs consistent even when the interface language changes. |
TOWS extends SWOT by checking relationships between external and internal factors from the opposite direction.
It helps move from a static list of factors to a relation-based strategy discussion.
You receive a relation map for SWOT and TOWS combinations. Each relation is shown as a simple on/off value, so you can see where the agent found a connection between two factors.
The output is intentionally reviewable. You can confirm, change, or skip the Human in the loop review before moving to strategy calculation.
| Relation group | Question answered by the agent | User review format |
|---|---|---|
| S&O | Do strengths support opportunities? | Relation cells shown as checked or unchecked values. |
| S&T | Do strengths reduce threats? | Relation cells shown as checked or unchecked values. |
| W&O | Do weaknesses limit opportunities? | Relation cells shown as checked or unchecked values. |
| W&T | Do weaknesses intensify threats? | Relation cells shown as checked or unchecked values. |
| TOWS | Do external factors affect internal factors? | Additional relation tables for OS, TS, OW, and TW. |
The System Algorithm counts confirmed interactions and combines them with priority weights assigned to SWOT factors.
This produces a score table for SO, ST, WO, and WT strategies, including unweighted and weighted values used to select the recommendation.
| Metric | Meaning | Used for |
|---|---|---|
| SWOT score | Sum of confirmed relations in the SWOT direction | Shows direct interaction strength. |
| TOWS score | Sum of confirmed relations in the TOWS direction | Shows reverse-perspective interaction strength. |
| Weighted score | Relations adjusted by priority weights | Reflects user-defined importance of factors. |
| Final score | Combined result used by the system | Determines the recommended strategy. |
S&O means an aggressive strategy, where strengths support opportunities. S&T means a conservative strategy, where strengths reduce threats.
W&O means a competitive strategy, where weaknesses limit opportunities. W&T means a defensive strategy, where weaknesses intensify threats.
| Code | Strategy | Business interpretation |
|---|---|---|
| SO | Aggressive strategy | Use strengths to capture opportunities and scale action. |
| ST | Conservative strategy | Use strengths to reduce threats and protect position. |
| WO | Competitive strategy | Reduce weaknesses to unlock opportunities. |
| WT | Defensive strategy | Limit exposure where weaknesses and threats reinforce each other. |
You receive a strategy review table with SWOT score, TOWS score, combined score, weighted score, final score, recommended strategy, and status.
The recommended strategy is calculated by the portal System Algorithm, not by an LLM. The algorithm uses reviewed relation maps and priority weights to compare the final scores of SO, ST, WO, and WT strategies.
| View element | Content | Decision value |
|---|---|---|
| Strategy score table | SO, ST, WO, WT rows with SWOT, TOWS, combined, weighted, and final scores | Lets the user compare strategies transparently. |
| Recommended strategy | Strategy with the highest final score | Shows the preferred strategic direction. |
| Status | Recommended or tie | Explains whether one strategy won or several strategies are tied. |
You receive a practical action plan based on the recommended strategy, the project context, SWOT factors, and the reviewed relation map.
The action plan is structured into phases, objectives, actions, owners, timeframes, expected outcomes, success metrics, and key risks.
| Action plan part | What it contains | How to use it |
|---|---|---|
| Phases | Sequential blocks of work | Use them as the roadmap for execution. |
| Actions | Concrete tasks inside each phase | Turn the strategy into operational steps. |
| Owners and timeframes | Who should act and when | Help organize responsibility and timing. |
| Metrics and risks | Success measures and key risks | Help verify whether the strategy is working. |
The system helps you move from an unstructured situation description to a readable SWOT matrix, reviewed dependency maps, an algorithmic strategy recommendation, and an AI-assisted action plan.
It is a decision-support workflow. It improves clarity and structure, but the user remains responsible for validating assumptions and making final decisions.
Contact
How to reach the creatorUse the contact email shown below for product questions, bug reports, cooperation proposals, and scientific contribution topics.
When reporting a problem, include the project type, page URL, current project stage, and a short description of what happened.
Useful feedback includes unclear workflow steps, incorrect AI outputs, missing methodology explanations, interface issues, or ideas for research-oriented improvements.
The more concrete the example, the easier it is to verify and improve the service.
The first version of the portal was used as a basis for scientific research that was published as an academic publication.
Version 2 reflects recommendations and design conclusions from that research, which is one of the theoretical arguments for developing this portal further.
You still have a question?
If you cannot find the answer in this policy section, contact the creator of the portal.
Scientific contribution
Swotmaker v2 is informed by research based on the first version of the service.
Open publication