Define the projects you actually want

Separate an internal assistant from deterministic workflow automation, systems integration and high-impact decision support. These projects demand different delivery skills and controls. State what your team builds, which platforms it supports and what happens after go-live.

A buyer should understand whether you are a rapid prototyping studio, an integration specialist or a long-term implementation partner before they request a proposal.

• Clear scope: route inbound service requests into a CRM with a human review path for exceptions.
• Unclear scope: automate the entire sales function without process ownership or acceptance criteria.
• Specialist fit: APIs, data governance, security, model evaluation, user experience or managed operations.

Qualify the opportunity before the pitch

A discovery call should determine whether the project is ready for a scoped proposal, needs a paid assessment or is not a fit. Start with the existing workflow and the business constraint, not the preferred model name.

• Current process, pain point and measurable business objective.
• Systems, integrations, data sources and access ownership.
• Sensitive data, privacy constraints, logging and human approvals.
• Budget range, project sponsor, buying process and timing.
• Acceptance criteria, monitoring, support and incident ownership.

How agency visibility and matching work

A useful agency profile explains capabilities, project boundaries and examples of fit. Buyers can assess relevance before contacting you. Any matching or priority depends on the buyer’s requirements and the agency’s suitability; listing visibility does not guarantee enquiries or deals.

Current plans: Free at SEK 0/month. Partner at SEK 995/month may receive priority matching where project fit is strong, without a guaranteed lead volume. The SEO & AEO agent is offered at a SEK 600/month introductory price with ongoing review and two relevant new pages per week, subject to current terms. Check the pricing page before committing.

Build a profile buyers can trust

Specific scope beats generic AI claims. Show what your team can implement and maintain, which decisions stay with the client and where you require specialist oversight. A good fit signal is sometimes an honest limitation.

• Three representative use cases with goals, systems and constraints.
• Evidence of integration, testing, security and operational ownership.
• Real delivery markets and project size; do not imply unverified offices.
• Discovery-to-pilot-to-production process with named responsibilities.
• Who should join the buyer’s first meeting.

When to decline an opportunity

If the buyer cannot grant legitimate access, lacks an accountable process owner or expects unreviewed decisions in a sensitive workflow, offer a bounded discovery phase or decline. A smaller number of well-scoped conversations is more useful than a calendar of impossible pitches.

Three signs an automation brief is sales-ready

1. There is a process owner. The buyer can describe today’s workflow and name the person authorised to approve a changed one. Without ownership, even a good prototype may never reach production.

2. Systems and data can be mapped. Someone can explain where the information lives, which APIs are available and what access can legitimately be granted.

3. Acceptance criteria are possible. The buyer can define how errors will be detected, where human review is required and what must work before go-live.

A simple qualification card can contain five fields: use case, process owner, systems, risk level and next decision. If most are unknown, offer discovery rather than a fixed-price build. That protects both the buyer and the agency’s delivery capacity.