Build with Claude · Deploy with NeoApps

Your business.
Your intelligence.
Your software.

Describe what your business needs in Claude Desktop, Claude Code, or a connected MCP client such as Codex. Build AI workers, automate workflows and create full-stack apps you own—then deploy and share them with NeoApps.AI.

Generated stack: .NET Web API + React admin UI · Build locally with Docker

claude · neoapps
you > Build a client portal for my firm
Clarifying users, records and approvals…
App + workflow + AI worker proposed
Review → Choose a path → Build → Deploy → Share
neoapps > Your business, running on your rules.
Why NeoApps.AI

Building got faster. Carrying the software forward still takes work.

Coding agents can now build full-stack apps and agents. The trade-off is that every change still needs the right business context, code review, and testing. When a project starts from scratch each time, repeated context and token costs can add up—and some generated code gets replaced instead of becoming a lasting product.

↻

Context has a cost

The model needs to understand your app, customer feedback, rules, and prior decisions. In our experience, repeated changes to a large codebase can increase token use while developers still review and approve the result.

▦

Good scaffolding still matters

Traditional generators and standard application structures remain useful. NeoApps combines a known .NET API, React UI, database schema, and workflows with AI that can help create and evolve the application.

⌂

You choose where it runs

Use the open-source generator locally, deploy through NeoApps Cloud, or run the app on infrastructure you manage. The generated code stays available for your team to inspect and extend.

Our experience

We have spent thousands of dollars building scalable applications and maintaining them. The first build is no longer the only challenge: a small customer request can mean reloading a lot of context, spending more tokens, and asking a developer to review code again. Our approach is to keep a durable application structure and use AI to help plan and apply changes to it, so the software can grow instead of being thrown away.

Frontier models are improving quickly. In our experience, customers still carry the work of supplying business context, managing repeated token use, and reviewing changes. We believe a proven generator approach—structured schemas and familiar application patterns—can make that work more reusable.

Where we fit: Platforms such as Replit Agent, Lovable, and Emergent show how far prompt-driven app creation has come. NeoApps.AI focuses on business applications: structured data, roles and permissions, approvals, audit trails, long-running workflows, and reusable AI agents alongside the app.

NeoApps.AI has been open source for more than two years, built from our 15-plus years of ERP development experience. GitHub stars are not the measure we care about most; the question is whether a team can inspect the code, build a useful application, and keep evolving it.

For teams with tighter controls: open source makes the code available for review and self-hosting, but it does not certify a deployment as compliant. The generated app can use an OpenAI-compatible model endpoint; a team may configure a local Qwen model served through a compatible runtime such as Ollama or vLLM, then validate that setup against its own security and compliance requirements.

How it works

Explain what you need. Make it yours.

Use Claude Desktop, Claude Code, or another connected MCP client as the conversational builder. NeoApps is growing from an open-source app generator into a connected home for your business knowledge, AI workers, workflows and apps.

01
Claude / Codex MCP

Describe the work

Explain your users, processes, data and approvals. Your connected coding assistant asks questions to turn the idea into requirements.

02
Review first

Approve the blueprint

Review the proposed data model, screens, roles and workflow before generation begins.

03
Choose your route

Build locally or with Cloud

Use the repository MCP to generate and run the source locally, or connect the hosted MCP for managed generation and deployment.

04
NeoApps Cloud

Activate, deploy and share

For managed deployment, activate a one-app or three-app plan or apply a promo code. NeoApps generates and deploys the app after activation.

.NET APIReact UIMySQLDockerMCPYour Git repository
Example: ClaimKit

From a consultant’s process to a client-ready SaaS.

SR&ED consultants manage complex client intake, project evidence and claim preparation. ClaimKit is a concrete example of expertise turned into software—and the first full-stack application we built and deployed with this workflow.

Product walkthrough · 8 min

See the ClaimKit experience

This video walks through how ClaimKit takes an SR&ED/R&D tax credit claim from client documents toward an audit-ready filing. Use the prompt below to build a similar app with Claude Desktop, then deploy it to NeoApps Cloud after review.

Watch on YouTube ↗
A result from our own work

ClaimKit: from years of SR&ED experience to a deployed app in about four hours.

Our work over several years on R&D claims showed us how much time it takes to collect expenses, wages, timesheets, project evidence, and review a claim's potential eligibility. We wanted an application for that process. Using the NeoApps.AI Code Generator with Claude Opus 5.5 on our regular Claude plan, our team generated the full-stack ClaimKit app from scratch, had the agent run its checks, and deployed it in about four hours. We then evaluated it against past claims and were impressed with the results.

The expert still matters. ClaimKit is meant to speed up intake, documentation, and evidence-backed review—not replace a consultant's judgment or make an official eligibility decision. In our estimate, a conventional agency project of this kind can take five to six months to reach an MVP, with significant development and AI costs along the way. Four hours is our experience with this build, not a delivery-time guarantee for every application.

A creator journey to demonstrate

Build ClaimKit with Claude Desktop.

Start with the process, not a blank code editor. For managed deployment, connect the hosted MCP, review the app plan, then activate payment or a promo code before Cloud generates and deploys the app. For a local build, use the repository MCP and keep the generated source in your Git project.

Build ClaimKit, a multi-tenant SaaS for SR&ED consultants. Help firms onboard clients, collect project details and evidence, track deadlines, and review claim packages with clients. First interview me about our real workflow, roles, data, approvals, and reports. Use the NeoApps.AI hosted MCP connected to this assistant. Inspect its available tools and show me the app plan, then wait for my review. Explain the one-app and three-app hosting plans, the Canada and US regions, and any runtime model costs. After I choose a plan and complete payment or apply a promo code, generate and deploy the app through NeoApps Cloud, verify its status, and return the live URL. Report what was actually completed and flag unsupported capabilities; do not assume integrations or service features.
Hosted deployment flow: Sign up at cloud.neoapps.ai, copy the MCP server details from cloud.neoapps.ai/mcp, and connect it to Claude, Codex, or another MCP client. Ask the assistant to use NeoApps.AI and paste your app idea. To generate and deploy immediately, activate the one-app or three-app plan with payment or a promo code from the NeoApps team. The app is generated and deployed after activation. The separate local generator flow remains available in the Cloud guide ↗
One connected platform

Own your intelligence. Own your workflows. Own your apps.

Your business knowledge can power the people, processes and software you build. These capabilities describe the NeoApps platform direction; today’s open-source foundation is the app generator and MCP workflow.

◎

Company intelligence

Bring together your SOPs, policies, documents and expertise. Apply access rules to the knowledge your agents can use.

✳

AI workers

Create focused agents with their own instructions, tools, knowledge, permissions and approval requirements.

↗

Business workflows

Connect triggers, decisions, actions and human approvals into repeatable processes.

▦

Full-stack applications

Build accounting apps, custom CRMs, ERPs, client portals and complete SaaS products around your process.

↥

Deploy and share

Deploy to Canada or the US. Each app stays in its selected region on later deployments; share its live URL with colleagues or customers.

⌘

Your code, your control

Start from an open-source foundation. Keep your app in your Git repository and choose how to extend it.

↻

Evolve the same app

Respond to customer feedback with structured schema and workflow changes. Use supported migrations to preserve existing data; review code changes before shipping. A focused app can grow into modular ERP and long-running workflows as requirements expand.

Available today: open-source full-stack generation, local development and NeoApps Cloud deployment via the repo MCP/CLI or hosted Claude connector. Product direction: a unified intelligence, agent and workflow studio.

Pick your path

Build it yourself. Share it. Or bring us in.

Use Claude and the open-source generator on your own, deploy to NeoApps Cloud, or ask NeoApps to scope a custom build and support engagement.

01 · Build it yourself

Build and host it yourself

Use Claude Desktop, Claude Code or Codex with the NeoApps MCP server. Keep the source and deploy on infrastructure you choose; configure a local model endpoint when your selected runtime supports it.

I want to build [describe my business app or AI worker]. Start by asking questions about users, processes, data and permissions. Check the NeoApps.AI schema and environment guidance. Show me a proposed plan and wait for my approval. Then use the available NeoApps tools to generate, build and run the app locally. Keep the source code in my project, explain how I can customize it, and show me options for hosting it myself. If I want to use a local model, check whether the app supports an OpenAI-compatible endpoint and explain how to configure my chosen Qwen model/runtime without sending prompts to an external provider.
Open GitHub setup guide

Use your own development environment and hosting setup.

03 · Build a custom solution

Build and operate a custom solution

Work with us on a tailored product, deploy it for your customers, or add experienced builders to your team.

I want to turn [describe my process or expertise] into software for my business and customers. Help me outline the custom application, agents, workflows and integrations I need. I may need NeoApps to build the solution, deploy and host it, maintain and support it, or provide experienced resources to work alongside my firm. Please prepare a discovery agenda and a proposal covering scope, timeline, ownership, deployment, maintenance and pricing.
Discuss a custom engagement

Custom apps, deployment, support, maintenance and team resources. Have an idea you want to build and own? Contact me; I’ll personally help you scope and build it.

MCP tools

Choose hosted generation or a local build.

For managed deployment, connect the NeoApps Cloud MCP and activate a plan or promo before the app is generated and deployed. For self-managed development, use the repository MCP to generate and run the source locally.

⌕

Check and plan

Review schema guidance, check your environment and preview an application plan before generation.

+

Generate and evolve

Create a full-stack app, change requirements, manage migrations and regenerate the frontend.

▶

Build and inspect

Run locally, review status and logs, and keep developing in your codebase with Claude or Codex.

Local generator: follow the repository setup guide to install and connect its MCP server. It registers with Claude Desktop and Claude Code and prints configuration for other MCP clients, including Codex. Use this route to generate and run source code on your own machine and host it on infrastructure you choose. View local MCP setup ↗

Hosted NeoApps Cloud: sign up at cloud.neoapps.ai, copy the MCP server details from the MCP page, and connect them to Codex, Claude, or another MCP client. Tell the assistant to use NeoApps.AI and describe your app. Choose the one-app or three-app plan and pay, or enter a promo code from the NeoApps team. Generation and deployment begin after activation.

See the repository for MCP setup and the current tool reference. View documentation ↗

What can you build?

Turn your expertise into an app.

Build tools for your own team, or package your know-how into software that customers can use and pay for.

Patient Intake Portal

Clinic, MSK, mental health and clinical research intake.

Legal Intake & Case Portal

Personal injury, IME and legal aid matter workflows.

Engineering Assessment Portal

Transport design review, asset inspection and safety audits.

SR&ED Documentation App

Software, manufacturing R&D and consultant multi-client claims.

Personal Finance App

Personal financial health, advisor and credit-union wellness.

Field Inspection App

Quality checks, maintenance and construction safety inspections.

Research Data Collection

Structured study data, participant records and review status.

Mental Health Intake & Monitoring

Private-practice and university counseling workflows.

Grant Application Portal

Government innovation and foundation application reviews.

Compliance Audit Workflow

Regulatory inspections, evidence, findings and corrective actions.

Vendor Qualification App

Manufacturing supplier onboarding and supply-chain reviews.

Student Intake & Support Portal

Admissions, wellbeing, accessibility and student support.

FieldOps 360

Dispatch, work orders, technicians, equipment, inventory and invoices.

Every featured scenario has a copy-ready Claude prompt below, alongside repository app ideas, agent concepts and the wider platform vision. Browse the existing NeoApps app library ↗

Claude prompt library

Start with a real use case.

Choose a prompt, copy it into Claude Desktop, Claude Code or a connected MCP client, and refine it through questions. Each prompt asks the assistant to inspect the available repository or Cloud MCP tools before it makes a blueprint or builds. The ideas draw from the repository app-ideas docs ↗.

Copy any prompt; shared build instructions are included.

Your workflow. Your apps.

Build it yourself with Claude, share it with your customers, or ask NeoApps to scope hosting and ongoing support.

Choose your path