TRL 6
SpaceOS positioning
Parsimoni describes SpaceOS as mission-specific TRL 6 technology. Treat qualification as configuration- and mission-dependent, not universal.
Mission brief · September 11, 2026
Space compute.
AI application layer.
A focused preparation brief for the conversation around Parsimoni, SpaceOS / SpaceRun, the satellite application layer, and where an AI-native build team can create measurable leverage without overclaiming flight heritage.
Confirmed: Miklos Tomka / ParsimoniMeeting: Ian / SpaceOSFocus: paid pilot → evidence → GTM
SpaceRunApp layer beside flight software
AI in orbitCompany-identified “Why now” driver
GoalOne buyer · one workflow · one pilot
01 · Executive brief
What matters before the room.
~$40M
Reported pipeline
The investor materials describe a roughly $40M pipeline across contracts, consortium bids and joint offers. Treat this as company-reported pipeline, not booked revenue.
2nd
In-orbit mission claim
The forwarded correspondence references a second in-orbit mission and current App Store / integration activity. Use the meeting to separate deployed capability from planned integration.
Miklos Tomka
CEO and co-founder of Parsimoni. The investor deck says he has two startups and one exit and visually associates him with INSEAD, Bain & Company and AllSight. Those are Parsimoni-provided biography claims until independently verified.
SpaceRun / App Store model
Parsimoni positions SpaceRun between applications and spacecraft flight software, aiming to let developers build portable applications across supported satellite platforms. That makes the collaboration wedge the application and workflow layer—not spacecraft control.
02 · Collaboration map
Highest-potential ways to work together.
AI application layer
Ship one useful non-safety-critical workload through SpaceOS.
Fit 94 / 100
Developer copilot
Turn docs, APIs, test constraints and packaging rules into an expert build assistant.
Fit 90 / 100
Ground ops intelligence
Incident triage, log summarization and operator decision support with human approval.
Fit 87 / 100
University funnel
AI-assisted intake, scoring and prototyping for their university use-case program.
Fit 82 / 100
Customer opportunity mining
Map operators, payloads, data products and high-value workflows into buyer-ready hypotheses.
Fit 78 / 100
Joint go-to-market
Earn this after a pilot proves buyer value and technical compatibility.
Fit 70 / 100
Recommended first move: AI application layer
Ask for one concrete workload they want deployed through SpaceOS. Build a thin demonstrator around image triage, change detection, onboard prioritization, anomaly summarization or operator decision support. Prove a deployable application—not autonomous spacecraft control.
Developer copilot
Use approved SpaceOS documentation, APIs, integration constraints and test procedures to help third-party developers move from idea → compatible package → evidence faster.
Ground ops intelligence
Start with historical operational data. Create incident clustering, log summarization, root-cause hypotheses and investigation paths with explicit human approval.
University funnel
Help turn their university program into a scalable intake, scoring, prototype and vetting system for high-value space application ideas.
Opportunity mining
Build a repeatable market-intelligence engine around satellite fleets, payload types, operator economics and data products, tied to named buyers and measurable value.
Joint GTM
Do not lead here. Earn it after one pilot demonstrates buyer value; then pair Parsimoni’s deployment path with our AI application and workflow layer.
03 · Meeting questions
Questions that force clarity.
What is deployed today?
Which SpaceOS capabilities are operating in orbit now, on which missions, and which claims are still integration work or roadmap?
What can a third party ship?
Which APIs, runtimes, resource limits, security boundaries and qualification steps exist today for an external application?
Who actually pays?
For the App Store model, who is the economic buyer, what revenue share is envisioned, and which near-term partner has willingness to pay?
Where is the bottleneck?
Is the constraint application supply, customer demand, spacecraft integration, certification, developer tooling, capital or engineering bandwidth?
What would make us useful in 30 days?
Ask them to name one deliverable they would value enough to sponsor, champion or introduce to a buyer.
Can Ian anchor a pilot?
Explore a JPL-adjacent, research, university or partner context where a non-safety-critical demonstrator would be credible.
Positioning guardrail: Speak as an AI-native product and integration team evaluating a space-compute collaboration. Do not claim existing NASA deployment, flight heritage or spacecraft-control capability unless independently substantiated.
04 · 30-day path
Turn the meeting into momentum.
Today · Qualify the wedge
Identify one workflow with urgency, data access and a stakeholder who can say yes.
Days 1–5 · Technical packet
Get docs, sample data, execution constraints, security boundaries, acceptance criteria and a named technical owner.
Week 2 · Prototype
Build the smallest useful AI application or developer workflow using non-sensitive or synthetic data where necessary.
Weeks 3–4 · Evidence
Measure latency, reliability, human time saved, model failure modes and integration friction. Decide whether there is a paid pilot.
05 · Decision frame
What James + Bo should leave knowing.
Technical fit
- Can we deploy safely into their supported environment?
- Can they give us a real sandbox or sample workflow?
- Does our layer complement—not duplicate—existing partners?
Commercial fit
- Is there a named buyer or budget owner?
- Does a pilot create measurable customer value?
- Can success turn into a reference and introductions?
Relationship fit
- Do they move quickly and share technical truth?
- Are roles and ownership explicit?
- Is the upside larger than a generic “partnership”?