Today, AscendCore, Inc. is officially incorporated as a Delaware C-Corporation.
The paperwork side of this is the boring part. The more important thing happening here is the bet we're making about where enterprise IT operations is going — and our willingness to put serious capital and serious engineering behind it for the long haul.
This post lays out three things: the problem we're solving, the thesis we're betting on, and what AscendCore is going to be when we're done.
The problem nobody is solving
If you've ever worked inside a Tier-1 IT support queue, you know the pattern. Seventy to eighty percent of the tickets that hit your engineers in any given week are the same six or seven categories — MFA resets, password resets, account unlocks, license assignments, group membership changes, VPN access requests, new-hire provisioning. The runbooks are well-defined. The systems involved are stable. The actions required are deterministic.
And yet a human engineer spends fifteen to twenty minutes on each one. Read the ticket. Verify the requester's identity. Open Okta or Entra. Find the user. Click the right button. Verify the change took. Update the ticket. Notify the user. Close it out.
Multiply that by hundreds of tickets a week, and you have an IT department where your most expensive headcount is doing the lowest-leverage work. The strategic projects — the migration, the security uplift, the modernization — keep getting deferred. Engineers burn out. Talent leaves. The cycle repeats.
Existing tools don't solve this. ITSM platforms like ServiceNow and Jira Service Management are systems of record — they catalogue tickets but don't resolve them. Horizontal AI platforms try to deflect tickets through chat — useful for FAQs, useless for actually executing the change in Okta. Workflow builders require an engineer to design and maintain the automation, which becomes its own job.
What's missing is a product built end-to-end for the IT-operations workflow: detect the request inside the chat tool where it already lives, classify it correctly, propose the remediation against your actual environment, get one-click human approval, execute it, verify it, and close the loop in seconds.
That's what AscendCore is.
What AscendCore is
AscendCore is the IT operations intelligence platform purpose-built for the teams keeping enterprise infrastructure running.
Concretely, today, it does three things:
- Lives natively in Microsoft Teams and Slack — where IT requests already happen. No new portal, no new chatbot URL. Your users open a ticket the way they already do, and AscendCore sees it.
- Resolves L1 ticket categories with human-in-the-loop approval — MFA resets, password resets, account unlocks, license assignment, group membership, new-hire provisioning, VPN access. The categories that consume the daily volume.
- Logs every action against a deterministic runbook with full approval audit trail — designed for the compliance posture enterprise IT actually requires.
The execution model is non-negotiable: every action that touches a production system flows through an explicit human approval gate. We will never silently execute against your environment. The IT manager sees the proposed remediation, the affected user, the runbook version, and the model's confidence — and approves with one click. This isn't a compliance checkbox. It's the architecture.
Why now: the vertical AI thesis
The dominant narrative in enterprise AI for the last 18 months has been horizontal: one platform that handles IT, HR, Finance, Customer Service, Procurement, and eight industries simultaneously, all on the same architecture diagram. Big TAM, big slide deck, big sales motion.
We believe this generation of horizontal AI is going to fragment exactly the way the horizontal CRMs of the early 2000s did. Salesforce showed up and owned sales. HubSpot owned inbound marketing. Zendesk owned customer support. The horizontal platforms either shrank to their best vertical or got acquired. The same consolidation is coming to AI automation — and IT operations is one of the largest, most underserved verticals waiting to be claimed.
Three reasons IT ops is going to fragment off into its own category:
- The constraints are completely different. Uptime SLAs measured in seconds. Change management protocols that require approvals before any production action. Audit trails that have to survive regulatory review. None of these constraints look like an HR ticket-deflection tool.
- The depth of integration matters more than the breadth. A native ServiceNow connector that can read incident history, update CMDB records, and trigger change workflows is worth more than 47 shallow connectors that can only open and close tickets. Generalist platforms are forced to build to the lowest common denominator.
- The buyer is different. IT directors and NOC managers don't pick automation tools the way HR ops leaders do. They care about blast radius, rollback paths, and integration with the monitoring stack — not deflection rates and survey scores.
A platform built for IT operations from the ground up — by people who have actually run NOC environments — is going to win this category. AscendCore is that platform.
What makes us different
Teams-native at full parity with Slack — from day one. Most incumbents started Slack-first because Slack started developer-friendly. The actual enterprise IT seat — the people who pay for help desk software — increasingly lives inside Microsoft 365. We built native Teams integration alongside Slack from day one. For Microsoft-first IT shops, this isn't a checkbox feature. It's a category of competitor that doesn't currently exist.
Runbook-first architecture, not chat-first. Competitors built around a chat metaphor end up with a sophisticated chatbot that can talk to engineers but can't execute against the systems engineers actually run. AscendCore inverts this. Runbooks are the load-bearing primitive — versioned, deterministic, auditable, reusable. Chat is the user interface that triggers them. This sounds like a small distinction. It's the difference between a product that resolves the ticket and one that just tells you what should happen.
Governance baked in, not bolted on. Every action requires explicit approval. Every approval is logged. Every execution is verified. The audit trail isn't a settings page — it's the architecture. This is what makes us deployable in environments where compliance review torpedoes horizontal-platform sales cycles.
Built by people who have been on call. This is the soft differentiator that's actually the load-bearing one. Our founder spent the last decade inside large carrier NOC environments where the difference between a 30-second runbook and a 30-minute runbook is the difference between an SLA met and an SLA breached. The product reflects that. The decisions about what governance has to look like, how an audit trail should behave, what an IT manager will actually trust — those are decisions made by someone who has been on the receiving end of poorly-designed automation.
Where we're going (the next 12 months)
We're not just building an L1 ticket-resolution tool. We're building the runbook-first operations brain for enterprise IT. The next 12 months on the roadmap:
- Predictive incident surfacing — pull telemetry from monitoring stacks (Datadog, PagerDuty, Splunk) and surface emerging issues before a ticket gets opened. The ticket queue as a lagging indicator becomes a leading indicator.
- Multi-system orchestration — runbooks that coordinate across PagerDuty + Datadog + ServiceNow + Okta + Entra as one engine. The platform thinks in incidents and outcomes, not in single-system actions.
- Per-organization runbook learning — the system improves from the patterns specific to each customer's environment, with explicit human-in-the-loop on every refinement. Your AscendCore deployment gets sharper the longer you run it.
- Graduated autonomy — as confidence builds in specific runbook categories, customers can graduate them from "human approval required" to "human notified" — at their own pace, controlled by them. We're not asking IT teams to trust autonomous AI on day one. We're giving them the dial.
- Compliance pipeline — SOC-2 Type I → Type II → ISO 27001 → FedRAMP. A credible posture aligned to the regulated-industry customers we're targeting at the upper end of mid-market.
This isn't aspirational decoration. It's the company we're building, in the order we're building it.
What this looks like for customers
Take a thousand-person company with a twelve-person IT team running on Okta + Microsoft 365. Industry benchmarks suggest roughly sixty percent of those engineers' time goes to L1 ticket categories — exactly the work AscendCore is designed to resolve. After deployment, that share drops dramatically. The reclaimed engineering capacity goes to the strategic work that's been deferred for years: the security uplift, the cloud migration, the next ITSM rollout, the projects that actually move the business.
Mean time to resolution changes too. A typical L1 ticket today takes hours from submission to closure depending on engineer availability and queue depth. AscendCore takes the same ticket from submission to verified resolution in seconds, with the full approval audit trail intact. Users stop waiting. Engineers stop context-switching. Both sides of the help desk get their time back.
That's not a marginal efficiency gain. It's a category change in how IT operations gets done.
Why Pittsburgh
Our founder grew up in this region and built his career here. Pittsburgh has a real and growing enterprise tech ecosystem — the CMU pipeline, the Innovation Works / AlphaLab / Idea Foundry triangle, and a meaningful concentration of Fortune-500 IT operations within driving distance. The cost-of-capital advantages relative to coastal hubs are real, and they translate into capital efficiency that early-stage investors notice.
We're not building from Pittsburgh as a civic statement. We're building here because the talent, the cost structure, and the proximity to enterprise customers make the math work — and because the kind of company we want to build tends to be built by people who have been close to the problem for a long time.
Where we are today
The platform is functional and live. We have working Slack and Teams integrations, real Okta and Entra MFA reset workflows running end-to-end with append-only audit logging, and an admin dashboard that lets an IT lead approve actions and review runbook history. We're targeting our first design partners in the mid-market IT segment now.
What we don't have yet — and won't pretend to: SOC-2 certification (Vanta enrollment in flight, target Type I by end of year), an independent penetration test (scheduled), or customer references (you could be one of the first). The honest framing of where we are lives on our security page, built around a Live / In Progress / Roadmap split rather than the trust-badge theater that's common in our space.
That transparency isn't a weakness. It's the same posture we're going to bring to every customer relationship — the same auditable, approval-gated, governance-first model we built into the product itself.
Who we want to talk to
If you're an IT leader — drowning in L1 ticket volume, watching your strategic roadmap slip, asking why automation hasn't actually delivered for your team — we built this for you. We're signing our first design partners over the next sixty days, and there is space at the table. The fastest way to start a conversation is hello@ascendcore.ai.
If you're an investor or advisor working in enterprise infrastructure or IT operations and the thesis above tracks, we'd love to talk too. The same address gets to us.
Pittsburgh is a good place to build a serious enterprise software company. AscendCore is going to be one of them.
— The AscendCore Team
Ready to see it in action?