speqtor.
Investor presentation
INVESTOR PRESENTATION · OCTOBER 2026

Cut software planning time.
From months to minutes.

OUR VISION

Remove the translation layer between
business intent and software implementation.

Today: verified plans. Tomorrow: AI implementation.01 / 10
02 / 10 The team

We’ve lived
this problem.

Twana Noori

Twana Noori

CEO & Founder

Product vision and customers.
Software experience at Tre, Evam and Kronans Apotek.

Pavan Kumar

Pavan Kumar

CTO & Co-founder

Technology and development.
Experience in code intelligence and large-scale systems.

Samuel Selomon

Samuel Selomon

Sales & Go-to-market

Customer relationships and sales.
A senior developer who understands what teams need.

Planned hires: two senior developers to build with Pavan, funded from month 1.
03 / 10 The problem

One request.
Months before development starts.

“Let customers choose a pickup point at checkout.”
01

Find the right teams

Checkout teamOrders teamDelivery team
02

Meetings & system analysis

Map dependencies across teams.

03

Write tickets

Translate the business request.

04

Wait in the backlog

Context fades while work waits.

05

Rebuild lost context

Read the same code again.

06

More clarification

Repeat discussions and analysis.

07

Start development

Finally ready to build.

Repeated discoveryLost business contextRepeated AI costs

An illustrative process that can take months. The teams involved depend on the request.

04 / 10 The solution

The same request.
A development plan in minutes.

“Let customers choose a pickup point at checkout.”
INPUT

Describe the
business request.

speqtor.

Analyzes your software
and maps the change.

OUTPUT
  • What needs to change
  • Which systems are affected
  • Clear instructions for developers

Your developers review the plan and build with their existing tools.

05 / 10 Customer value

Less preparation.
A faster start.

TIME

Fewer meetings.

Spend less time finding out how the systems work.

CLARITY

Fewer handoff gaps.

Keep the business request connected to the development work.

AI COST

Less repeated analysis.

Reuse system knowledge instead of making AI start over.

WHY NOW

AI can write the code.
Enterprises still need to define the right change.

Speqtor connects business requests to the system context coding agents need.

Customer economics · illustrative example

Six people spending four hours on discovery at an assumed fully loaded cost of SEK 800 per hour equals SEK 19,200 per request. This excludes delay and rework.

Illustration only, not a measured customer result. Pilot comparisons will include discovery time, review effort and AI costs before and after Speqtor. We will quantify savings only after measuring both workflows.

06 / 10 Early traction

10 companies engaged.
All conversations progressing.

10 LARGE SWEDISH COMPANIES · TWO CURRENT STAGES
3

Ready to test the pilot

Moving into product evaluation.

7

In ongoing discussions

Continuing through the process.

Founder-reported pipeline, October 2026. Interest is established; product value and willingness to pay remain to be validated.

NEXT PROOF POINTS

Time saved per reviewed plan. Repeat usage. Conversion to paid contracts.

What the pilots need to prove

Compare the same type of request with and without Speqtor: time to a reviewed plan, clarification rounds, review corrections and AI usage. Track repeat use, the budget owner’s purchase decision and the agreed annual price.

Ten companies are in the pipeline, including three ready to test. These are not ten active pilots or paying customers. No completed pilot results, paid conversions or renewal data are claimed.

07 / 10 Market & business model

Start in Sweden.
Expand within every customer.

INITIAL CUSTOMER

Mid-sized to large enterprises with multiple teams,
repositories and complex existing systems.

GO-TO-MARKET

Founder-led pilots. Prove value. Expand.

Sweden → Nordics → Europe → Global
Target buyer CTO / Head of EngineeringInternal champion Product or architecture lead
ENTERPRISE SAAS

Annual contracts by team coverage and deployment size.

€30K2 teams / year
€150K10 teams / year

Illustrative pricing: €15K per team / year. Start with one business area, expand across the organisation. Pricing to validate in pilots.

Market validation & revenue scenario

A named customer list before a market headline.

Build the initial Swedish account list around mid-sized and large companies with internal development teams, multiple repositories and complex systems. Qualify each buying organisation by supported stack, a concrete use case, budget ownership and procurement access. Deduplicate companies that share a buying decision.

Expand the same qualification process to the Nordics and Europe. TAM and SAM remain to be established; the previous account ranges were unverified assumptions and have been removed.

18-month revenue scenario, not market size
Paying customer targetAssumed initial annual contractAnnualised exit revenue
15–25€30K€450–750K ARR

A conditional scenario, not committed revenue or revenue earned over the 18 months. The €1M budget assumes no customer revenue. Expansion to €150K is excluded from this calculation.

Commercial assumptions to test.

Target budget owner: CTO or Head of Engineering. Likely internal champions: product and architecture leads. Confirm the actual buyer during pilots, including security and procurement requirements.

Illustrative annual pricing is €15K per covered team: two teams imply €30K; ten imply €150K. Validate willingness to pay, discounts and deployment scope. Customers normally cover their own AI usage. Growth comes from repeatable onboarding and wider team coverage within existing customers; delivery effort and margins still need measurement.

08 / 10 Competition & moat

One business request.
A clear plan for every team.

CURSOR

Helps developers plan, write and test code.

SOURCEGRAPH

Helps teams find and understand code.

SPEQTOR

Shows what a business request means for the company’s systems.

What must change, which teams are involved and what each team needs to build.

WHY SWITCHING GETS HARDER

Once all repositories are analysed, switching means rebuilding and validating that system knowledge.

Reviewed decisions and established workflows make replacement more costly over time.

Competitive context & defensibility

Capabilities overlap. Cursor can research codebases, plan changes, write code and run tests. Sourcegraph provides code search and code understanding across repositories. Speqtor’s intended position is the shared planning layer for business and engineering, connecting a requirement to changes across existing systems.

Our switching-cost thesis: after Speqtor has analysed a company’s repositories and mapped their relationships, a replacement needs to recreate or migrate that knowledge and validate its accuracy. Customer-reviewed decisions and established workflows can add further migration effort. Repository analysis alone is reproducible; the stronger moat is accumulated, validated context and daily use. These switching costs remain to be proven with customers, rather than assumed from indexing alone.

Product references checked October 2026: Cursor ↗ · Sourcegraph ↗

09 / 10 The journey

Start with planning.
Grow into implementation.

NOW

Working product.

Enterprise interest.
Pilots ready to start.

NEXT 18 MONTHS

Repeatable Swedish GTM.

Pilots to paying customers.

15–25 customers
NEXT

Nordics & Europe.

Expand a proven sales model.
Growth round after Swedish validation.

LONG-TERM VISION

Describe a change. Get code ready for review.

YOUDescribe the changeSPEQTORMap impact & planCODING AGENTSWrite code & run testsYOUR TEAMReview pull requests

Speqtor coordinates changes across repositories. Your team approves before merge.

18-month milestones & execution
MONTHS 1–6

Validate

Measure value with pilot customers.

3 paying customers
MONTHS 7–12

Focus

Find the strongest customer segment.

8–12 paying customers
MONTHS 13–18

Repeat

Win similar customers and expand usage.

15–25 paying customers

Proposed targets. Success means regular use, measurable value and renewals. Twana and Samuel lead customers and sales. Pavan leads development with two additional senior developers, budgeted from month 1 at €6,500 gross per person per month. Product priorities are reliability, analysis quality and pilot feedback. Geographic expansion and AI implementation are subsequent ambitions, not deliverables promised within this round.

Next funding stage

The current €1M round funds two additional senior developers, Swedish validation and a repeatable sales process. A subsequent growth round would support Nordic and European expansion once retention, customer value and sales repeatability justify it. Timing and size depend on those results and runway.

Long-term investor outcome

Build a durable enterprise software business with recurring revenue and expansion within customers. One possible exit route is a strategic acquisition by an enterprise software or developer-tool platform seeking the connection between business requirements and implementation. This is an option, not a committed process or a claim of buyer interest.

10 / 10 The investment

Raising €1M.

18 months to strengthen development and build repeatable sales in Sweden.

18MONTHS + RESERVE

Existing team plus two senior developers from month 1. €900K operating budget and €100K reserve (10% of the round). No customer revenue assumed.

18-month budget and salary assumptions
Planned use of €1,000,000
CostBudget
Team salaries, employer costs and cost allowance€680,000
Infrastructure, hosting and monitoring€55,000
AI usage for development, testing and demos€45,000
Sales tools, marketing and events€30,000
Customer visits, travel and workshops€26,000
Legal, accounting, insurance and security support€36,000
Equipment, work tools and workspace€28,000
Reserve€100,000
Total€1,000,000
Five people budgeted for 18 months
RoleMonthly gross salary / personStart18 months incl. employer costs
Twana, Pavan and Samuel (3 people)SEK 50,000 ≈ €4,545Month 1€343,636
Two additional senior developers€6,500Month 1€327,600
Additional team cost allowance and rounding——€8,764
Team allocation€680,000

Planning exchange rate: €1 = SEK 11, not a live exchange-rate quote. Existing salaries remain SEK 50,000 per person per month. A 40% planning allowance covers employer contributions, pension, insurance and holiday supplements for all five people; actual costs depend on employment terms and country. Each new developer costs €9,100 per month including this allowance (€18,200 combined). Existing team cost is SEK 3,780,000 ÷ 11; totals are rounded to whole euros. The team allocation includes an additional €8,764 allowance for changes in employment costs and rounding.

Average planned operating spend is approximately €50,000 per month, excluding reserve. The €100K reserve equals 2 months at that spending rate and also covers currency and cost uncertainty. All five people are funded from month 1; a later hire leaves additional headroom. Customers normally cover their own AI usage. The operating budget supports hosting, product development, testing, demos, direct sales and company administration.

Let’s build the next chapter.

invest@speqtor.ai