Axamy
Voice-first AI workspace for teams that coordinates work and manages follow-ups.
Website: https://axamy.com/
Cover Block
Public sources
| Field | Detail |
|---|---|
| Company | Axamy |
| Tagline | Voice-first AI workspace for teams that coordinates work and manages follow-ups. [axamy.com] |
| Headquarters | San Francisco/Berkeley, United States [Crunchbase] |
| Founded | 2025 [Crunchbase] |
| Stage | Pre-Seed [Crunchbase] |
| Business Model | SaaS |
| Industry | HR / Future of Work |
| Technology | AI / Machine Learning |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Conor Healy, John Honovich, Duc Tran, Thang Vu [Crunchbase, retrieved 2026] |
| Funding Label | Pre-seed |
| Total Disclosed | Approximately $725,000 [Crunchbase] |
Links
Public sources
- Website: https://axamy.com/
- Google Play: https://play.google.com/store/apps/details?id=com.axamy.app
- Careers: https://wellfound.com/company/axamy-1
Executive Summary
PUBLIC Axamy is building a voice-first AI workspace for teams, and it merits investor attention because the company is trying to turn routine conversations into durable organizational memory and automated follow-through, a problem that remains weakly served by chat, project management, and note-taking tools alone [axamy.com] [Axamy - Apps on Google Play] [PulseGate]. Founded in 2025 and based in the San Francisco/Berkeley area, the company is still at a very early stage, but its public materials point to a clear product thesis: teams should be able to talk through work, have the system capture decisions and commitments, and then have software persistently coordinate the next actions by phone, text, email, mobile, and workplace integrations [Crunchbase] [axamy.com] [axamy.com, retrieved 2026].
The differentiation, to the extent it can be assessed from public evidence, sits less in a standalone model claim and more in workflow design: Axamy says it remembers context across interactions, tracks training performance over time, and connects into Google Drive, Gmail, Calendar, and Slack so follow-up happens inside existing operating systems rather than in a separate dashboard [axamy.com, retrieved 2026] [axamy.com] [The Axamy Blog, retrieved 2026]. That product posture could resonate if the company proves it reduces managerial overhead in environments where missed handoffs and status chasing are common, though the public record does not yet establish customer adoption, retention, or deployment scale [axamy.com] [PulseGate].
The founding bench has some signal, even if the public biographies are uneven. Conor Healy is identified publicly as CEO and cofounder, with prior experience at IPVM, while cofounder and CPO John Honovich is listed by Crunchbase as the founder of IPVM in 2008; other named founders include Duc Tran and Thang Vu, with Jack Corcoran appearing in operations or BizOps roles in public profiles [Conor Healy - Cofounder of Axamy, retrieved 2026] [Crunchbase] [Jack Corcoran - Operations @ Axamy | Harvard '25, retrieved 2026].
On financing, the available public record supports a pre-seed company with disclosed funding of about $725,000, although the exact timing is not fully settled across databases, and no lead investor is confirmed in the evidence provided [Crunchbase] [Signalbase, retrieved 2026] [recentfunding.com, retrieved 2026]. The business model appears straightforward SaaS, with public pricing starting at $10 per month for Starter and $19 per month for Grow, which suggests a bottom-up entry point even as the company recruits a Founding Sales Lead in San Francisco, a sign that the go-to-market motion is still being built [axamy.com, retrieved 2026] [Wellfound, retrieved 2026].
Over the next 12 to 18 months, the key questions are basic but material: whether Axamy can show repeatable usage beyond founder-led deployments, whether voice-first coordination produces meaningfully better follow-through than incumbent collaboration tools, and whether the team can translate a low entry price into expansion revenue without losing product simplicity [axamy.com] [Wellfound, retrieved 2026]. The setup is early, the product thesis is coherent, and the evidence burden now shifts from concept and messaging to proof of customer pull.
Company-stated, unverified -- This section relies heavily on company materials and directory profiles, with limited independent corroboration beyond Crunchbase and public profile pages.
Taxonomy Snapshot
| Axis | Value |
|---|---|
| Stage | Pre-Seed |
| Business Model | SaaS |
| Industry / Vertical | HR / Future of Work |
| Technology Type | AI / Machine Learning |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (3+) |
| Funding | Pre-seed, total disclosed about $725,000 |
How the Company Got Here
PUBLIC
Axamy appears to be a very young company still defining itself in public through product language rather than corporate disclosures. The clearest facts are the simplest ones: Crunchbase lists Axamy as founded in 2025 and based in the San Francisco Bay Area, while the company website presents it as a coordination product that follows up with teams by phone call, text, email, or a mobile app until work is completed [Crunchbase] [axamy.com].
The public chronology is thin but directionally useful. A 2025 founding date on Crunchbase sets the starting point, and the company site now shows an active product surface with a homepage, pricing page, technology page, and blog content describing workflow coordination, organizational memory, and integrations with Google Drive, Gmail, Calendar, and Slack [Crunchbase] [axamy.com]. The homepage footer uses "Axamy, Inc." and carries a 2026 copyright notice, which supports the view that the business is operating publicly as a U.S. software company, although no state filing details were available in the cited materials [axamy.com].
The early milestones that can be stated conservatively are therefore limited to public launch and basic go-to-market signals. By 2026, Axamy had published self-serve pricing starting at $10 per seat per month for Starter and $19 per seat per month for Grow, alongside messaging that positions the product as a voice-led workspace for team coordination and follow-through [axamy.com]. That is enough to establish an initial commercial posture, but not yet enough to verify customer adoption, legal structure beyond the website footer, or a fuller operating history from primary public records [axamy.com].
Lightly corroborated -- Based on Crunchbase and Axamy's website; core founding and location details are partially corroborated, while legal entity detail rests on company website copy alone.
Product and Technology
MIXED Axamy is positioning the product around one clear behavior: work gets captured in conversation, then the system keeps following up until someone closes the loop. On Axamy's homepage, the company says it follows up with teams by phone call, text, email, or a mobile app until the work is done [axamy.com]. Public product pages and blog posts describe a broader workspace that turns conversations into shared knowledge, decisions, commitments, and actions, with a voice-first interface meant to let users talk through priorities rather than triage them across scattered tools [axamy.com].
The product surface, as publicly described, extends beyond note capture into coordination and lightweight workflow management. Axamy says the platform can create, assign, track, and follow up on knowledge transfer, feedback, issues, and scheduling, and that it gives leaders real-time visibility across the team without requiring direct oversight [axamy.com]. The company also says the system identifies recurring blockers and missed handoffs, and recent blog material points to integrations with Google Drive, Gmail, Calendar, and Slack, which suggests Axamy is trying to sit above existing workplace systems rather than replace them outright [axamy.com].
The technical claims are directionally interesting, but most of the evidence remains company-authored and should be read as product intent rather than independently verified performance. Axamy's technology page describes a real-time organizational model with memory, automations, and preferences, while a training-focused post says the system stores user performance over time and uses that history to shape the next training step [axamy.com]. Those statements imply an architecture centered on persistent context and cross-channel agent behavior, but there is no verified public demo, third-party case study, or press reporting in the provided materials that confirms how well those capabilities work in production [axamy.com].
Company-stated, unverified -- This section relies primarily on company website and blog claims, with no independent public verification of product performance or deployments.
Where the Demand Sits
PUBLIC This market matters now because the cost of coordination has risen with tool sprawl, distributed teams, and heavier AI experimentation, while the public evidence around Axamy still points more to category formation than to a clearly measured market share claim [axamy.com, retrieved 2026].
Axamy sits at the intersection of team collaboration, workflow automation, and enterprise AI assistants, but the available source set does not include a named third-party TAM, SAM, or SOM estimate specific to the company’s category [Crunchbase, retrieved 2026]. In that absence, the cleaner approach is to treat the product as participating in analogous markets rather than asserting a bespoke market size. The company’s own materials describe a voice-first AI workspace that captures conversations, turns them into shared knowledge and commitments, and follows up across phone, text, email, mobile, and workplace tools such as Slack, Gmail, Calendar, and Google Drive [axamy.com, retrieved 2026]. That feature mix places it near the operational overlap of collaboration software, work management, and AI-enabled productivity tooling, not a single mature software budget line.
The demand signal visible in public materials is straightforward. Axamy repeatedly frames the problem as follow-through: chasing updates, scattered tools, bottlenecks, knowledge transfer, scheduling, and missed handoffs [axamy.com, retrieved 2026]. Those are ordinary management problems, but the company is trying to solve them through continuous conversational capture and automated follow-up rather than through another dashboard or manual project tracker [axamy.com, retrieved 2026]. If that framing resonates, the adoption driver is less about replacing one incumbent suite outright and more about reducing the coordination tax that grows as teams add communication channels and AI copilots.
A conservative market map is below. These are analogous public markets, not direct measurements of Axamy’s attainable revenue pool.
| Analogous market claim | Figure | Relevance to Axamy |
|---|---|---|
| Global collaboration software market, 2024 (analogous market, Grand View Research) [Grand View Research, February 2025] | $18.37B | Closest fit for shared team coordination and workplace collaboration |
| Global workflow management system market, 2024 (analogous market, Grand View Research) [Grand View Research, January 2025] | $11.43B | Relevant to task routing, follow-up, and process orchestration |
| Global intelligent virtual assistant market, 2024 (analogous market, Grand View Research) [Grand View Research, March 2025] | $15.79B | Relevant to conversational interfaces and AI-driven assistance |
The table suggests Axamy is entering a broad, already funded software spend area rather than inventing a category from zero. It also suggests that the company will likely be sold against existing budgets for collaboration, operations, or AI productivity, which can help demand, but it also sharpens the burden of differentiation.
The clearest tailwinds are organizational, not purely technical. Hybrid work and multi-tool environments raise the value of systems that preserve context across channels, while the current AI cycle has made buyers more open to software that automates routine managerial follow-up and synthesizes unstructured conversations into actions [axamy.com, retrieved 2026]. Axamy’s blog and product pages emphasize memory, persistent context, and pattern detection across recurring blockers and missed handoffs [axamy.com, retrieved 2026]. Those claims line up with a broader buyer appetite for software that can operate on top of fragmented communication rather than requiring teams to change behavior first.
The adjacent and substitute markets are just as important as the primary one. In practice, Axamy could be compared with project management software, internal knowledge tools, meeting intelligence products, workflow automation platforms, CRM tasking layers, and general-purpose workplace copilots, depending on the buyer’s entry point [axamy.com, retrieved 2026]. That adjacency is commercially useful because it expands the number of budget owners who might care, but it also means the company is unlikely to enjoy a clean procurement lane early on. A voice-first interface may be a wedge, yet the real test is whether it produces measurably better follow-through than text-first incumbents or lightweight AI layers added to existing systems.
Macro and regulatory considerations are present even if the current public record is thin. Because the product captures conversations, stores organizational memory, and coordinates actions across communications channels, enterprise buyers are likely to scrutinize data handling, retention, permissions, and worker transparency before broad deployment, especially in regulated or compliance-sensitive settings [axamy.com, retrieved 2026]. The integrations with Gmail, Calendar, Google Drive, and Slack make the product more useful, but they also increase dependency on external platforms and permission scopes [axamy.com, retrieved 2026]. For a company at this stage, those are not disqualifying issues, but they do shape sales friction and expansion pace.
Lightly corroborated -- This section relies on Axamy company materials for category definition and product-market framing, plus third-party analogous market reports from Grand View Research for sizing context.
Competitive Landscape
MIXED Axamy appears to sit between collaboration software, workflow automation, and AI meeting or memory tools, with its public positioning centered less on document creation and more on persistent follow-through across calls, texts, email, mobile, and workplace software [axamy.com, 2026] [axamy.com].
The public record is thin on named direct rivals, so the cleanest way to map competition is by substitute category rather than startup-to-startup comparison. On one side are incumbents that already own team workflow and communication surfaces, notably Slack, Google Workspace, and calendar or email systems that Axamy says it integrates with [axamy.com]. Those products already sit where work is discussed and assigned, which matters because a new coordination layer must either displace familiar habits or attach itself to them. On the other side are adjacent AI tools, especially meeting assistants, note capture products, and task managers that turn conversations into summaries or action items. Axamy's own materials point to a broader ambition: not only capture, but repeated follow-up until work is completed, plus memory across channels and training contexts [axamy.com, 2026] [axamy.com].
That distinction is interesting, but today it looks more perishable than durable on the evidence available. The company's nearest visible edge is product design, a voice-first workflow that lets teams talk through issues and have the system coordinate next steps, alongside integrations with Google Drive, Gmail, Calendar, and Slack [axamy.com, 2026] [axamy.com]. If that interaction model produces higher user compliance than dashboards or manual project tracking, it could create a real wedge. Still, the underlying ingredients, cross-channel messaging, task extraction, memory, and integrations, are all categories where larger platforms or well-funded application vendors can move quickly. Without public evidence of proprietary data, entrenched distribution, regulated workflow ownership, or a distinctive customer base, the advantage looks early and largely product-led rather than structurally protected [Crunchbase] [Wellfound].
The exposure is clearer than the moat. Slack and Google do not need to match Axamy feature for feature to make adoption harder; they only need to keep improving coordination inside products teams already use every day. That channel ownership is significant because Axamy's website itself signals dependence on those ecosystems through its listed integrations [axamy.com]. The company is also exposed to specialist training, performance, and operational workflow software if buyers want point solutions instead of a horizontal team layer. Axamy's public case rests on one system handling knowledge transfer, feedback, scheduling, blocker detection, and follow-up [axamy.com, 2026]. Buyers often like that vision, but they also ask whether one layer can outperform purpose-built systems in each job.
The most plausible 18-month scenario is that the competitive outcome turns on whether voice-first coordination becomes a daily operating habit or remains an interesting overlay. Slack is the most plausible winner if buyers continue to prefer adding lightweight AI features inside an incumbent communications stack they already administer. Axamy is the more plausible winner if teams prove willing to adopt a separate orchestration layer because automated follow-through, especially via phone, text, and email, drives measurably better execution than reminders inside chat or project tools alone [axamy.com, 2026]. In that same frame, a likely loser if incumbents close the workflow gap is any standalone coordination product without a strong proprietary dataset or captive distribution channel, and on the current public evidence Axamy still needs to show that its memory and follow-up layer can become that kind of asset [Crunchbase] [axamy.com].
Opportunity
PUBLIC
The prize here is unusually large if Axamy can turn a narrow workflow assistant into a system of record for conversations, commitments, and follow-through across a team, because that would place it closer to operating infrastructure than to a point productivity tool [axamy.com].
The headline opportunity is not simply better note-taking or task capture. On Axamy's own description, the product sits in the middle of everyday managerial work: it captures conversations, converts them into shared knowledge and commitments, follows up by phone call, text, email, or mobile app, and now connects into Google Drive, Gmail, Calendar, and Slack [axamy.com]. If that behavior becomes reliable at team level, the reachable outcome is a cross-functional coordination layer for small and mid-sized organizations that want visibility without adding management overhead [axamy.com]. That remains an early and company-stated proposition, but it is reachable rather than purely aspirational because the product already spans capture, memory, follow-up, and integrations, which are the core components needed for a persistent workflow surface rather than a single-use AI feature [axamy.com].
The upside paths look different depending on where the wedge holds. The table below frames three concrete routes from an early voice-first assistant to a much larger software position.
| Scenario | What happens | Catalyst | Why it's plausible |
|---|---|---|---|
| Team coordination wedge | Axamy becomes the default operating layer for frontline and managerial teams that need constant follow-up across calls, messages, and shared tools | The product's multi-channel follow-up and integrations reduce missed handoffs in live operating environments [axamy.com] | Axamy already presents itself as following up until work is done and has added Google Drive, Gmail, Calendar, and Slack integrations, which suggests a product aimed at daily execution rather than occasional summarization [axamy.com] |
| AI-native manager console | Axamy wins with leaders who want real-time visibility into goals, blockers, training, and accountability without adding another layer of reporting | Better performance in training, issue escalation, and recurring blocker detection creates an executive use case [axamy.com] | The company says the system identifies recurring blockers, missed handoffs, and training gaps, and gives leaders real-time visibility and follow-through across teams [axamy.com] |
| Organizational memory platform | Axamy grows from an assistant into a persistent memory layer that remembers goals, people, actions, and preferences across channels and sessions | Durable memory quality improves enough that teams trust the system as a shared source of truth [axamy.com; Google Play] | Axamy's public materials repeatedly emphasize lasting memory, one continuous relationship across channels, and preferences attached to agent actions, which is the architecture required for a sticky knowledge layer [axamy.com; Axamy - Apps on Google Play, retrieved 2026] |
What compounding looks like is fairly clear in the product design, even if public proof is still thin. Every additional conversation can improve the system's memory of goals, commitments, blockers, and user preferences; better memory should improve follow-up quality; better follow-up should increase the amount of work routed through the platform; and that, in turn, deepens the organizational context available to the product [axamy.com]. The early signs of that flywheel are visible in the way Axamy describes one continuous relationship across phone, browser, or Slack, plus adaptive training flows that remember where a user struggled and use that memory to shape the next step [Axamy - Apps on Google Play, retrieved 2026; axamy.com]. If that loop works in practice, switching costs rise over time because teams are not just buying automation, they are accumulating operating context inside the system.
The size of the win is harder to quantify from public evidence because no market-sizing source or clean public comparable was provided in the research set. Even so, the scenario worth watching is straightforward: if Axamy were to become a trusted coordination layer for thousands of paid teams on seat-based pricing that starts at $10 per month for Starter and $19 per month for Grow, the business could move from lightweight SaaS entry points into a much larger expansion motion through management, training, and workflow orchestration [axamy.com]. That does not support a defensible valuation figure from the available sources, so any enterprise-value statement here would be conjecture. The more disciplined framing is that the upside case rests on Axamy earning a system-of-work position, not a feature position, and the public product surface does show the ingredients of that ambition [axamy.com].
Company-stated, unverified -- This section relies primarily on Axamy's own website, pricing page, product pages, and blog, with limited third-party corroboration for product behavior and no independent public evidence for market size, customer adoption, or valuation benchmarks.
Sources
Public sources
[axamy.com, 2026] Axamy - We call until the work gets done | https://axamy.com/
[Crunchbase, 2026] Axamy - Crunchbase Company Profile & Funding | https://www.crunchbase.com/organization/axamy
[Axamy - Apps on Google Play, 2026] Axamy | https://play.google.com/store/apps/details?id=com.axamy.app
[PulseGate] Axamy · PulseGate | https://pulsegate.ai/startups/axamy
[The Axamy Blog, 2026] The Axamy Blog | https://www.axamy.com/blog
[Conor Healy - Cofounder of Axamy, 2026] Conor Healy - Cofounder of Axamy | https://www.axamy.com/about
[Jack Corcoran - Operations @ Axamy | Harvard '25, 2026] Jack Corcoran - Operations @ Axamy | Harvard '25 | https://wellfound.com/company/axamy-1
[Signalbase, 2026] Axamy Secures $350K | Signalbase | https://www.trysignalbase.com/news/funding/axamy-secures-350k
[recentfunding.com, 2026] Axamy: AI inoculation against bureaucracy: horizontal | https://recentfunding.com/companies/axamy/
[Wellfound, 2026] Axamy Careers - Insights and Opportunities | https://wellfound.com/company/axamy-1
[Grand View Research, February 2025] Collaboration Software Market Size, Share & Trends Analysis Report | https://www.grandviewresearch.com/industry-analysis/collaboration-software-market-report
[Grand View Research, January 2025] Workflow Management System Market Size, Share & Trends Analysis Report | https://www.grandviewresearch.com/industry-analysis/workflow-management-system-market-report
[Grand View Research, March 2025] Intelligent Virtual Assistant Market Size, Share & Trends Analysis Report | https://www.grandviewresearch.com/industry-analysis/intelligent-virtual-assistant-market
[axamy.com, 2026] Axamy - Pricing | https://www.landing.axamy.com/pricing
Articles about Axamy
- Axamy Builds an AI Workspace With a Phone in Its Hand — The pre-seed startup, founded by IPVM's John Honovich and Conor Healy, is pitching a persistent AI agent to coordinate and chase down tasks.