Twana Noori
Product vision and customers.
Software experience at Tre, Evam and Kronans Apotek.
Remove the translation layer between
business intent and software implementation.
Product vision and customers.
Software experience at Tre, Evam and Kronans Apotek.
Technology and development.
Experience in code intelligence and large-scale systems.
Customer relationships and sales.
A senior developer who understands what teams need.
Map dependencies across teams.
Translate the business request.
Context fades while work waits.
Read the same code again.
Repeat discussions and analysis.
Finally ready to build.
An illustrative process that can take months. The teams involved depend on the request.
Analyzes your software
and maps the change.
Your developers review the plan and build with their existing tools.
Spend less time finding out how the systems work.
Keep the business request connected to the development work.
Reuse system knowledge instead of making AI start over.
Speqtor connects business requests to the system context coding agents need.
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.
Moving into product evaluation.
Continuing through the process.
Founder-reported pipeline, October 2026. Interest is established; product value and willingness to pay remain to be validated.
Time saved per reviewed plan. Repeat usage. Conversion to paid contracts.
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.
Mid-sized to large enterprises with multiple teams,
repositories and complex existing systems.
Founder-led pilots. Prove value. Expand.
Annual contracts by team coverage and deployment size.
Illustrative pricing: €15K per team / year. Start with one business area, expand across the organisation. Pricing to validate in pilots.
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.
| Paying customer target | Assumed initial annual contract | Annualised 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.
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.
What must change, which teams are involved and what each team needs to build.
Once all repositories are analysed, switching means rebuilding and validating that system knowledge.
Reviewed decisions and established workflows make replacement more costly over time.
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 ↗
Enterprise interest.
Pilots ready to start.
Pilots to paying customers.
15–25 customersExpand a proven sales model.
Growth round after Swedish validation.
Speqtor coordinates changes across repositories. Your team approves before merge.
Measure value with pilot customers.
3 paying customersFind the strongest customer segment.
8–12 paying customersWin similar customers and expand usage.
15–25 paying customersProposed 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.
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.
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.
18 months to strengthen development and build repeatable sales in Sweden.
Existing team plus two senior developers from month 1. €900K operating budget and €100K reserve (10% of the round). No customer revenue assumed.
| Cost | Budget |
|---|---|
| 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 |
| Role | Monthly gross salary / person | Start | 18 months incl. employer costs |
|---|---|---|---|
| Twana, Pavan and Samuel (3 people) | SEK 50,000 ≈ €4,545 | Month 1 | €343,636 |
| Two additional senior developers | €6,500 | Month 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.
[email protected]