--- title: "What’s included in a Shipasub subscription" slug: /blog/whats-included locale: en h1: "What’s included in a Shipasub subscription" answer_block: "A Shipasub subscription ($899/mo) includes web apps, APIs and backends, landing pages, automations, bug fixes, feature work, database and API integrations, and deployment support—plus unlimited queued requests, one-at-a-time shipping, and unlimited revisions. It does not include heavy native mobile, video production, 3D or game engines, or enterprise-scale infrastructure." author: Aneudy Abreu brand: Shipasub / aneudyac.com status: seo-pass hreflang_pair: /es/blog/que-incluye --- # What’s included in a Shipasub subscription > A Shipasub subscription ($899/mo) includes web apps, APIs and backends, landing pages, automations, bug fixes, feature work, database and API integrations, and deployment support—plus unlimited queued requests, one-at-a-time shipping, and unlimited revisions. It does not include heavy native mobile, video production, 3D or game engines, or enterprise-scale infrastructure. Clear scope prevents mismatched expectations. This page walks through what [Shipasub](https://www.shipasub.com) covers, what it deliberately leaves out, how requests and revisions work, and what turnaround looks like—so you can decide if the subscription matches the work you actually need. ## Included: web, APIs, landings, automations, and more Everything below is in scope for the monthly plan at **$899 USD/mo**. Brief notes on why each category fits a sequential senior-engineering subscription: ### Web apps (React, Next.js, Vue, Astro) Product UIs, admin tools, and customer-facing apps built with modern web stacks. Typical shapes include dashboards, authenticated product surfaces, and content-heavy sites. Sequential delivery works well here because features can be sliced into reviewable requests. ### APIs and backends (Node, Python, Go) Services, endpoints, auth flows, and server-side logic. Backends pair naturally with web apps and integrations; clear contracts and acceptance criteria keep the one-request-at-a-time model efficient. ### Landing pages and marketing sites Marketing pages, campaign landings, and SEO-minded static or hybrid sites. These are often well-scoped requests with visible outcomes—ideal for a shared board and quick review cycles. ### Automations and integrations Connecting tools, triggering workflows, syncing data between systems. Automations reduce manual ops; they ship cleanly when inputs, outputs, and failure modes are defined upfront. ### Bug fixes and feature additions Incremental product work on existing systems. Fixes and features are the everyday texture of an ongoing subscription: you queue them as they appear, prioritize, and ship without opening a new project quote each time. ### Database work and API integrations Schema changes, queries, migrations, and third-party API wiring. This sits next to backend work and often unlocks product features that would otherwise stall. ### Deployment and DevOps support Getting builds live, environments configured, and releases repeatable. Deployment support closes the loop from “it works locally” to “it ships in production.” Across these categories, the work is executed by Aneudy Abreu—founder-engineer with 10+ years shipping production software across React, Node, Python, databases, APIs, and cloud—with no junior bench and no outsourcing. Portfolio-style examples of work types include SaaS-style dashboards, API integrations, and marketing sites as categories of delivery—not invented client case studies. ## Not included: honest boundaries Shipasub is explicit about what it does **not** cover: - **Heavy native mobile development** — deep iOS/Android native apps are outside the subscription. - **Video production or editing** — creative media pipelines are a different craft. - **3D modeling or game engines** — specialized toolchains and timelines. - **Enterprise-scale infrastructure** — large-org platform and infra programs are not the product. Saying no keeps delivery quality high on what is in scope. If your primary need is one of the excluded categories, a different specialist or a full-time hire is the clearer path. For how that hire comparison is framed on cost alone, see [subscription vs hiring a full-time developer](/blog/subscription-vs-hiring-a-developer). Plan details: [pricing](https://www.shipasub.com/#pricing). ## How requests and revisions work You add **unlimited requests** to a shared task board (Trello or Linear). You have **full visibility** into queue and progress. Requests ship **one at a time**. Workflow in short: 1. Capture the request on the board with context and success criteria. 2. When capacity opens, that request becomes the active focus. 3. You review the deliverable. 4. **Unlimited revisions** continue until you are satisfied. 5. The next queued item starts. “Unlimited” applies to how many items you can queue and how many revision rounds you can request—not to parallel engineers working every ticket simultaneously. Prioritization on the board is your control surface. The model is designed for clarity, not for running ten streams at once. This is the same loop described in [software development as a subscription: how it works](/blog/software-development-subscription). More on the person shipping the work: [About](https://www.shipasub.com/about). ## Turnaround expectations Most requests are delivered within **two days on average** (average 48-hour delivery). Complex work may take longer. Expectations are set upfront so scope and timing stay aligned. What speeds delivery: - Clear acceptance criteria - Access to repos, environments, and credentials when needed - Fast feedback on reviews What slows delivery: - Undefined scope - Blocked access - Large “do everything” tickets that should be split Pause and cancel remain available anytime: **no contracts, no lock-in**. Billing cycles are **31-day periods**; unused days bank (for example, use 20 days and bank 11). That pairs well with scope clarity—you use capacity when the queue is real, and pause when it is not. ## Start with the right scope If your backlog looks like web apps, APIs, landings, automations, fixes, features, databases, integrations, and deploys—Shipasub is built for that list. If your backlog is mostly native mobile, video, 3D/games, or enterprise infra—look elsewhere first. - **Book 15 minutes:** [https://cal.com/aneudyac/15min](https://cal.com/aneudyac/15min) - **Subscribe:** [https://buy.stripe.com/00wbJ1bPXalZgrAbRq0x200](https://buy.stripe.com/00wbJ1bPXalZgrAbRq0x200) - **Site:** [https://www.shipasub.com](https://www.shipasub.com) Scope clarity is part of the product. Know what is included, know what is not, and subscribe when the match is real.