Insights
Practical guidance on building and running software.
What we have learned scoping, pricing, building and securing software for businesses, written for the people who make the decisions.
More from PapelSoftware
Each article answers a question clients ask us before or during an engagement. No gated downloads, no sign-up required.
Product
How to scope a software project before you hire anyone
A few days of structured thinking before you contact a vendor will save weeks of discovery and make proposals comparable. Here is the process we would follow on your side of the table.
5 min read
Security
Preparing your app for an enterprise security questionnaire
What security reviewers are actually looking for, the practices that answer most of their questions, and the documents to prepare before the first questionnaire lands.
5 min read
Engineering
React Native or native Swift and Kotlin: how we decide
Both approaches produce good apps in the right circumstances. These are the questions we use to choose between them, and the trade-offs we put in writing before a project starts.
4 min read
Business
Fixed bid, hourly or subscription: paying for software development
The pricing model decides who carries the risk when scope changes and whether your vendor's incentives match yours. A fair comparison of the three common options.
4 min read
Product
Keeping a website editable without breaking it
Structured content, sensible roles, a review step, version history and a few automatic guardrails let your team edit freely while the site holds together.
4 min read
Engineering
Technical decisions explained for the people who pay for them.
AI
Building assistants and AI features that are accurate and safe to ship.
Business
Budgets, contracts and working with a development partner.
Security
Practices and paperwork that larger customers ask for.
Product
Scoping, content and the decisions that come before code.
- How to scope a software project before you hire anyoneA few days of structured thinking before you contact a vendor will save weeks of discovery and make proposals comparable. Here is the process we would follow on your side of the table.5 min read
- Keeping a website editable without breaking itStructured content, sensible roles, a review step, version history and a few automatic guardrails let your team edit freely while the site holds together.4 min read
Have a project that raises these questions?
Talk to an engineer about scope, platform choices, AI features or security requirements. You'll get a written recommendation either way.