netlify AISES — The structural intelligence layer professional writing has never had.
Co-Founder Search Open · Beta Q3 2026

The structural intelligence layer for professional writing.

AI for sentences exists. AI for structure doesn't. That's the gap AISES is built to close.

of
Market Size · 2026 → 2029
$0.0B → $0B
Co-Founder Equity
Meaningful
Commensurate with contribution & risk
Writing Formats
Novel
Co-Founder Ramp
Flexible
Part-time start · pace tied to readiness
The Role

The hard engineering starts here.

The product vision is documented and the build is underway. What comes next is domain-adaptive AI that understands the difference between a legal brief, a screenplay, and a dissertation. That's not a feature request. That's a company-defining problem, and we're looking for the person who wants to solve it.

01
Complete
Technical blueprint
02
Live
Interactive prototype
03
• Now
MVP build
PRIORITY HIRE
Actively Recruiting
CTO / Technical Co-Founder
Apply for this role →
What you'd own
Domain auto-detection from raw text — distinguishing a legal brief from a dissertation from a screenplay before any explicit signal
Multi-model orchestration with a shared structural intelligence core, not five disconnected products
Rejection-learning pipeline that adapts to each writer's voice without explicit feedback signals
Cross-document memory architecture that compounds intelligence across a user's full history
Bias review as a parallel audit layer across six intersectional dimensions, architected from day one
Production infrastructure, model strategy, and engineering team build-out — every major technical decision
What we're looking for

You've shipped production AI systems — not just trained models, but taken them to real users. What matters most is that you've gone from idea to product. You see a gap this size and think about the system you'd design to fill it.

Production AI / ML NLP / LLM Fine-Tuning Systems Architecture Shipped Products
Terms
Equity Meaningful co-founder equity. Standard 4-year vest, 1-year cliff. No pre-committed split — specific terms direct.
Commitment Part-time start · full-time tied to mutual readiness, not a deadline
Location US-based preferred · remote-friendly · founder in NY
The Platform

Six capabilities.
No other platform
has all of them.

Each one addresses a problem that existing writing tools have ignored entirely. Not incremental improvements — a different category of tool. From spatial manuscript mapping to AI that lives inside the document and learns how each writer works, these capabilities form the structural intelligence layer that no platform in the market has attempted to build.

I.
AI Corkboard

The entire manuscript, mapped spatially. Every chapter becomes a card. Every structural beat is visible at once. Writers see the architecture of what they’ve written before touching a single word — and finally know if structure is the actual problem.

See the Architecture
II.
Ghost Editor

An AI collaborator that lives inside the document — not a chatbot the user pastes text into. It reads the full manuscript, understands the structural arc, and when a section isn’t working, drafts three alternatives to choose from. The writer’s voice stays theirs. For collaborative projects, it maintains separate voice profiles per author and includes configurable AI contribution disclosure.

Lives Inside the Document
III.
Bias-Reviewed

Every AI suggestion passes through an independent intersectional audit layer — checking for cultural, linguistic, and representational fairness across six dimensions, including where identity categories intersect. Built into the architecture from day one. No current writing tool is designed this way.

Bias detection assists human review and does not guarantee bias-free content.

Built In, Not Bolted On
IV.
Rejection Learning

AISES is designed to learn how each writer writes. When a user consistently ignores a suggestion — because the “flaw” it’s flagging is actually their style — the system stops flagging it. No settings to configure. The tool adapts to the writer’s voice, not the other way around.

Adapts to the Writer
V.
Cross-Document Intelligence Enterprise

Every document knows the user’s history. A law firm’s new brief checks against prior briefs on the same matter. A series novelist’s Book 2 knows every fact established in Book 1. The intelligence compounds over time — becoming institutional knowledge that lives nowhere else.

Compounding Intelligence
VI.
Adversarial Review

Before submission, Ghost Editor attacks the writer’s own work — responding as a hostile reader who wants to put the book down, a literary agent looking for reasons to pass, or opposing counsel finding the weakest argument. No other writing tool does this.

Stress-Test Before Submission
Why AISES

Other tools touch structure.
None make it the architecture.

AISES sits above sentence-level tools like Grammarly and Word — they live at a different layer. The real competitive set is the small group of tools writers actually consider when they need to work on the shape of a manuscript: Scrivener, Plottr, Fictionary, Sudowrite, and general-purpose AI. Here's how AISES compares on the dimensions that matter for structural editing.

AISES features reflect the designed architecture. The product is in active development.

Capability Scrivener Plottr Fictionary Sudowrite ChatGPT / Claude AISES
AI text generation No No ~ Limited revision suggestions Core feature Core feature Ghost Editor — contextual, in-document drafting
Document structure map ~ Manual corkboard ~ Manual planning board ~ Story-arc visualization ~ Story Bible (manual) No AI Corkboard — auto-generated from manuscript
Arc & pacing analysis No ~ Template-based (Save the Cat, etc.) 38 story elements, scene-by-scene ~ Beats feature ~ Via long prompt Ghost Editor — AI structural diagnosis on the live draft
AI voice adaptation No No No No ~ Basic memory Rejection learning — adapts to each writer's style
Multi-timeline visualization No Strong (its core) Single-timeline focus No No Core to memoir & dual-timeline fiction, integrated with structural analysis
Domain auto-detection Creative only Fiction/screenwriting only Fiction only Fiction only Generic, no specialization 5 domains — auto-detected on upload
Bias-reviewed suggestions No No No No No 6-dimension intersectional audit
Works across Google Docs, Notion, Word Standalone app Standalone app ~ DOCX import only ~ Web only ~ Via copy-paste Cross-platform by design
EU AI Act compliance ~ N/A — no AI ~ N/A — no AI Not confirmed Not confirmed ~ Partial Architected from day one
Cross-document intelligence No No Single-manuscript No No Document history informs every new doc
Adversarial review mode No No No No ~ Via prompt only Ghost Editor — hostile reader, agent, or opposing counsel
Role-based team AI No No ~ Editor/author collab No No Author / Editor / Reviewer / SME / Compliance — 5 roles + custom (Enterprise)
AI contribution audit No No No No No Every suggestion tracked — % AI-assisted, % human
The Bigger Picture

Creative writing is where
we start. It’s not where we stop.

Creative is the beachhead — highest structural complexity, clearest unmet need, strongest community signal. The same engine expands to academic, business, technical, and legal writing in later rounds. One structural intelligence core, format-adaptive across all five. That single-engine commitment is the moat — and the engineering challenge the co-founder owns.

Development Roadmap
✓  Blueprint
Technical blueprint, 12-format creative writing architecture
Complete
✓  Prototype
Interactive prototype live
Complete
MVP Build
Self-funded development underway
Now
Beta & Users
Closed beta with writers, collect usage data, iterate on feedback
Q3 2026
Seed Round
$5M @ $20M post — engineering team, creative-writing domain training, model fine-tuning. Opens post-MVP, post-CTO onboarding.
Q4 2026
Series A
Multi-format traction, revenue, expand to all 5 domains
2027–28
Launch · Beachhead
Creative Writing

12 formats: fantasy, mystery, romance, science fiction, literary fiction, historical fiction, thriller/horror, young adult, middle grade, short fiction, memoir, and creative nonfiction. Narrative structure detection, character intelligence, pacing analysis, and format-specific tools — from clue placement in mystery to relationship arcs in romance to truth-contract integrity in memoir.

Series A · Expansion
Academic Writing

Research papers, dissertations, grant proposals. Citation management across APA, MLA, Chicago, and IEEE. Argument structure analysis, methodology verification, and auto-formatting for 100 priority journal templates.

Series A · Expansion
Technical Writing

API documentation, engineering specs, user manuals. Procedure verification with step-by-step logic flow, standards compliance for ISO/IEEE/ANSI, version control integration, and automated changelog generation.

Series B · Enterprise
Business Writing

Proposals, reports, executive communications. Tone calibration across formality levels, audience-appropriate register, persuasion enhancement with argument weakness detection, and compliance flagging for GDPR, HIPAA, and SOX.

Series B · Enterprise
Legal Writing

Contracts, briefs, motions, compliance documents. Jurisdiction-specific compliance across federal, state, and local law. Bluebook citation verification, precedent discovery, contract clause analysis, and missing clause detection.

Founder
Shara Lopossa, Founder of AISES
Shara Lopossa
Writer · Visual Artist · AISES Founder
New York
LinkedIn

I got lost in my own manuscript —
so I designed the way out.

I spent years writing Daughter of Lunacy, a memoir about growing up alongside my mother’s mental illness, told across two timelines. I knew the story intimately — every scene, every line, every decision I made and second-guessed. And still, I couldn’t see it. Not the shape, not the structure, not how it all held together.

When you’re deep inside your own writing, working line by line, the overall architecture begins to disappear. That loss of perspective becomes even more pronounced when you’re weaving multiple timelines into a single narrative. You can feel when something isn’t working, but you can’t always see why.

So I tried to force visibility in every way I could.

Every tool made me faster. Not one helped me see.

I printed the manuscript and rearranged the scenes across the floor. I hired editors whose revisions reshaped the story in ways that weren’t mine. I turned to AI tools that could only see fragments, returning insights that never connected.

I kept running into the same limitation: every solution could operate at the sentence or section level, but none could show me the structure of the work as a whole. They could improve the writing line by line, but they couldn’t tell me if the document itself was structurally working.

I needed a way to see that structure clearly and dynamically, without losing control of my own voice. So I built it.

AISES is a system that maps, visualizes, and analyzes the structure of an entire document — not in fragments, but as a complete, living architecture. It is not built to rewrite the work or replace the writer’s judgment, but to surface the structural layer that is otherwise difficult to see.

I started by solving the problem for myself, creating a way to make the structure of a full manuscript visible. Then I expanded that thinking across academic, business, technical, and legal writing, recognizing that while the content changes, the underlying challenge remains the same.

All writing has structure. But structure has never had its own tool.

AISES is built to make that structure visible — for the first time.

FAQ
For co-founder candidates