Service moment and users
Explain what someone is trying to accomplish, who they are, what exists now, where trust or time is lost, and what a useful result would change.
Direct brief / no public form
Describe the service moment in plain language.
Email or call Logan directly. The first note can be short, but it should connect what a person needs to the Swedish content, accessibility, information, systems, staff work, transaction, failure, acceptance, and maintenance behind it.
Swedish content and accessibility
Name the Swedish reviewer, required languages, plain-language concerns, keyboard and assistive-technology needs, document issues, devices, and who approves accessibility evidence.
Identity and information
Describe accounts, BankID or other identity needs only if actually in scope, important personal information, permissions, tracking, retention, requests, and professional ownership.
Vendors and transaction route
List hosting, analytics, communications, support, AI, files, payment, settlement, refunds, invoices, VAT or accounting owner, and suppliers that affect release.
Existing systems and failure
Identify integrations, current code, staff tools, account owners, fragile dependencies, degraded modes, recovery, support route, rollback, and unacceptable failure conditions.
Acceptance and maintenance
Share the business approver, Swedish reviewer, technical evidence, production authority, hard deadline and reason, post-release owner, maintenance expectation, and response boundary.
Contact Logan
Use direct email or phone.
Do not send passwords, private keys, payment-card data, government identifiers, health records, or other sensitive material in an initial message.
A message does not create a project. Delivery begins after both sides settle feasibility, screening, the defined scope, decision duties, commercial terms, secure access, reviewer availability, and a signed agreement.