About
A software company that sells development by the month.
PapelSoftware LLC is a Delaware limited liability company based in the United States. We build and maintain web and mobile applications for businesses on subscription plans, and we make the software products we use to run them.
What we do
Two lines of business that support each other. The development team builds client applications; the products keep those applications running after launch.
Development subscriptions
Clients pick a plan based on how many requests they want in progress at once. A lead engineer, engineers and a product designer work through the client's queue and release every week.
Software products
Our products, currently in early access, built from the tooling we needed for client work.
- Papel Copilot
- An in-app AI assistant for your product, powered by Claude.
- Papel Sites
- Manage your website's pages, blog and forms, with Claude to help write.
- Papel Cloud
- Managed hosting and deploys for web apps and APIs on AWS.
- Papel Monitor
- Uptime checks, error tracking and public status pages.
Why a subscription instead of a project quote
Fixed-bid projects ask you to describe everything you'll need before you've seen any of it working. Hourly contracts make every new idea a budget conversation. Both push the relationship toward negotiating scope rather than building the right thing.
A subscription fixes the cost and leaves the order of work to you. You decide what goes into the queue and what comes first. When priorities change, items move; the invoice doesn't. You can pause or cancel when you no longer need us, so we have to keep earning the renewal every month.
It also matches how software actually lives. Most of an application's cost comes after launch: upgrades, fixes, new features and hosting. A monthly plan covers that work without a new contract each time.
What we believe
Six principles that shape our contracts, our process and the way we talk to clients. Each one is a commitment you can hold us to.
You own what you pay for
We work in your GitHub or GitLab organization from the first day. Code, designs and documentation produced under a paid plan belong to you, as set out in our Terms of Service.
If you leave, nothing has to be handed over because it was never ours. That keeps us honest: we have to earn the renewal, not rely on lock-in.
Small releases, every week
Work ships in small pieces on a fixed weekly cadence, with release notes and a preview link before anything reaches production.
A small release is easier to review, easier to roll back and makes progress visible. When a week slips, we tell you before Friday and explain why.
Published, flat pricing
Every plan has a published monthly price in US dollars. There are no hourly invoices, setup fees or change-order surcharges.
A fixed price moves the conversation from budget to priorities. Annual billing is the same plan at a lower rate, and you can cancel at the end of any billing period.
Write it down
Specs before code, notes with every release, architecture decisions recorded in your repository and incident summaries after anything serious.
Written decisions survive staff changes on both sides. The next engineer, ours or yours, should be able to pick up the work without a meeting.
Say no early
If a request is out of scope, a bad idea for your users or something we can't do well, we say so before work starts, not after the invoice.
A clear no on day one costs far less than a vague yes that turns into a missed deadline.
Boring technology in production
We choose well-supported, widely used tools for anything your business depends on, and keep experiments out of the critical path.
Popular, stable tools are easier to hire for, easier to secure and still supported in five years. You shouldn't need us to keep your software alive.
How the company is organized
Every development subscription is staffed with the same four roles. Your plan decides how much capacity they give you, not which roles you get. On smaller plans, one person may cover the engagement lead and lead engineer roles.
The people in these roles work on your account directly. We don't pass your work to subcontractors you haven't been told about.
Engagement lead
Your main point of contact for the subscription. Owns the roadmap and the queue order with you, writes the weekly report, and is the first escalation point if something isn't working.
- Roadmap and priorities
- Weekly report
- Plan and scope questions
Lead engineer
Responsible for the technical direction of your product. Writes specs for each request, reviews every pull request and decides how releases are cut and deployed.
- Specs and architecture
- Code review
- Release and rollback
Engineers
Build features, fixes and integrations across web, mobile and infrastructure, write the tests that ship with them and answer questions in your shared channel.
- Implementation
- Automated tests
- Staging previews
Product designer
Turns requests into flows and interfaces before engineering starts, maintains your design system and checks accessibility and usability on staging.
- UX flows and screens
- Design system
- Accessibility review
How we choose work
We would rather turn a project down than take it on and do it badly. Before we start, every engagement passes four checks.
- There is a real user problem
- We ask who will use the software and what they do today without it. If nobody can answer that yet, we suggest a smaller first step, such as a prototype or a design sprint, before a full build.
- A subscription is the right shape
- Our model suits ongoing product work. For a one-off task that will never need changes, a subscription may not be the best value, and we'll say so.
- We can do it well
- We take on web, mobile, cloud and AI work in the stacks listed below. If a project needs specialist skills we don't have, such as embedded firmware, we decline rather than learn on your budget.
- It meets our Acceptable Use Policy
- Some work we won't do, even when it's legal. The list is part of our contract with every client.
What we won't build
We don't build or host software for businesses whose primary activity is in these categories:
- Gambling, betting, lotteries or games of chance for money
- Adult content or services
- Weapons, ammunition, explosives or their components
- Unlicensed financial services, including money transmission and digital asset trading platforms
- Illegal or recreational drugs, and products sold on unproven health claims
- Multi-level marketing, pyramid schemes or debt collection
- Software built for spam, phishing, unauthorized access or collecting personal data without a lawful basis
- Regulated activities that need licenses the client can't demonstrate
The full list is in our Acceptable Use Policy.
Technology we use
Our default stack for new work. On an existing product, we work in the stack you already have, and only propose changes with a written reason.
| Area | Tools and standards | Why |
|---|---|---|
| Web applications | TypeScript, React, Next.js, Node.js | Server-rendered by default for speed and search visibility. |
| Mobile apps | React Native, Swift, Kotlin | Cross-platform where it fits, native where performance or platform APIs need it. |
| Data | PostgreSQL, Redis, S3-compatible object storage | Standard formats you can export and run anywhere. |
| Cloud and delivery | Amazon Web Services, Docker, GitHub Actions or GitLab CI | Infrastructure changes go through code review, like application code. |
| AI features | Anthropic's Claude through the Anthropic API | Commercial terms under which inputs and outputs aren't used for training. |
| Design | Figma, design tokens, WCAG 2.2 AA as the accessibility target | Designs and components handed over with the code. |
| Quality | Unit, integration and end-to-end tests in CI; code review on every change | Tests run on every pull request before anything merges. |
| Operations | Papel Monitor and Papel Cloud, or the tools you already use | Uptime checks, error tracking and backups from the first release. |
Where we work
PapelSoftware LLC is a US company, formed in Delaware, and our clients are US businesses. You sign a US contract, pay in US dollars and are covered by US law, as set out in our Terms of Service.
Our team works remotely, so our process is built for distance: written specs, recorded demos, shared channels and a fixed weekly cadence that doesn't depend on anyone being in the same room.
Support hours are Monday to Friday, 9:00 a.m. to 6:00 p.m. Eastern Time, excluding US federal holidays. Weekly calls are scheduled in your time zone.
Company details
The entity you contract with and pay. These details match our invoices, Terms of Service and payment receipts. Support questions go to the support center.
See also security practices and Terms of Service.
- Legal name
- PapelSoftware LLC
- Entity type
- Limited liability company
- State of formation
- Delaware
- Founded
- 2024
- Website
- papelsoftware.com
- Billing currency
- US dollars, monthly or annual
- Mailing address
- TODO: Street address, TODO: City, TODO: ST TODO: ZIP, United States
- General inquiries
- [email protected]
- Sales
- [email protected]
- Support
- [email protected]
- Support hours
- Monday to Friday, 9:00 a.m. to 6:00 p.m. Eastern Time
- Billing
- [email protected]
- Legal
- [email protected]
- Phone
- +1 (000) 000-0000
Want to see if we're a fit?
Tell us about your product and where it's stuck. We'll reply within one business day with next steps.