Business + market

Q9–Q12: model, customers, competitors, USP

Claim no customer count and no market size until the owner supplies sourced figures. The competitor list stays empty until names arrive.

6 open input slots in this group
Q9

In a few words, tell us about your company's business model. e.g. B2G, B2B, B2C, B2B2C etc.

B2B. Clients pay a one-time fee for setup, deployment, and training in their own environment, then a monthly fee for ongoing service (upgrades, retuning, support, and quarterly reviews).
Fee-based work is the standard starting point across ASKA engagements. Equity is taken occasionally, where the engagement is structured that way.
Source: application-draft.md ## Q9
Q10

What's the size of your customer base? How do you intend to acquire customers in the new market? TAM, SAM and existing customer base if any.

Customer base: no customer count is documented, so none is claimed.
Documented clientele: founders raising capital, companies commissioning infrastructure, and operators restructuring their finances or holdings. One delivered engagement is named by type only: a custom trading interface (Vibetrade) built for a trading-firm client.
[NEEDS INPUT: number of paying or pilot customers today, if any.]
TAM and SAM: [NEEDS INPUT: total and serviceable market figures with sources, or one line confirming they are not yet sized.]
Acquisition in Qatar: [NEEDS INPUT: one or two sentences on the planned path, for example direct outreach, local partners, or program channels.]
Live deployments exist (named in Q5). The service is sold around client deployments, not as self-serve signups.
  • number of paying or pilot customers today, if any.
  • total and serviceable market figures with sources, or one line confirming they are not yet sized.
  • one or two sentences on the planned customer acquisition path in Qatar, for example direct outreach, local partners, or program channels.
Source: application-draft.md ## Q10
Q11

List your direct competitors, both currently and in the future (support your answer with links to your competitors' websites). Please list the companies and their URLs.

[NEEDS INPUT: names plus website links, one per line, for each direct competitor today and each expected one. No competitor list is documented. Suggested shape once the owner supplies names:
1. Name, website link, one line on how it differs from Proteus.
2. Name, website link, one line on how it differs from Proteus.]
  • names plus website links, one per line, for each direct competitor today and each expected one. No competitor list is documented.
Source: application-draft.md ## Q11
Q12

What is your Unique Selling Proposition when compared with competitors in the market? Please support your answer with a brief SWOT Analysis. / a

USP: Proteus is an open-core, local-first team of six AI roles under human direction, sold with hands-on setup inside the client environment.
The kit is open source under Apache-2.0. It can run on local models, hosted models, or a mix, with privacy helpers (Redact flags sensitive text, Gist suggests a topic, Title drafts a label).
Each role hands real work to the next (research, plan, design, code). A separate reviewer checks the result. The client sees what is ready and what is still uncertain.
Pricing is public: 9,300 USD one-time for setup, deployment, and training, plus 540 USD per month for ongoing service.
Scope limits are stated in writing, including no guaranteed uptime, response times, savings, or model performance.

SWOT:
Strengths: open-source kit, local-first deployment, human review built into the pipeline, public pricing, stated honesty standard (no fabricated credentials).
Weaknesses: setup needs terminal comfort and manual steps, no one-command installer yet, no conversational setup agent yet, public kit not yet independently demonstrated end to end.
Opportunities: [NEEDS INPUT: one or two target segments or use cases the owner wants to claim, e.g. regulated teams that need local deployment.]
Threats: [NEEDS INPUT: one or two pressures the owner sees, e.g. named rival platforms or model-provider shifts.]
  • one or two target segments or use cases the owner wants to claim for Opportunities, e.g. regulated teams that need local deployment.
  • one or two pressures the owner sees for Threats, e.g. named rival platforms or model-provider shifts.
Source: application-draft.md ## Q12