Start by testing whether a Portland brand needs an installed product at all
A lot of demand in this market comes from consumer brands: apparel, outdoor, food and drink, retail, membership organisations. For that kind of buyer the honest first question is not which studio to hire but whether an icon on a home screen is the right instrument. A responsive site reaches everyone immediately, costs less to keep alive, and does not require anyone to make a decision before they can use it.
The case for an installed product rests on specific things a browser cannot do well: reliable notifications, background work, hardware and sensor access, genuine offline use, stored credentials for fast repeat purchase, or a usage frequency high enough that people will accept the install. If your honest answer is that customers visit a handful of times a year, a mobile app will win a small, loyal minority and be ignored by everyone else. A studio worth hiring will say this out loud during the pitch rather than quoting what you asked for.
Installed is easy, retained is the thing you are actually buying
The metric most mobile app briefs carry is downloads, and it is the least useful one available. What determines whether the investment pays is how many people are still opening the product weeks later, and that is decided by the first session, by whether the product does something the website could not, and by whether notifications are useful rather than promotional.
Change the acceptance criteria accordingly. Instead of a launch date and a feature list, agree what retention at week one and week four would count as success, and require the analytics needed to see it to be part of the first release rather than a later phase. Ask each candidate to describe a product where those numbers were disappointing and what they changed in response. The firms who only show launch screenshots have never had to answer that question.
The platform commission belongs in your business case, not in a footnote
If you sell digital goods, subscriptions or memberships inside the product, both stores take a share of the transaction and require you to use their payment system for that class of purchase. Physical goods and services delivered in the real world sit outside that rule, which is why an outdoor brand selling jackets and a membership organisation selling access face completely different economics for the same build.
Work out which category you are in before design begins, because the answer changes pricing, the wording you are permitted to use, whether you may link to your own checkout, and how subscriptions are cancelled and refunded. Ask each supplier to explain the rules as they apply to your specific model. Vague familiarity here is expensive: a submission rejected over payment terms can hold a launch for weeks, and restructuring a subscription after release means migrating people who already pay.
Design led and engineering led studios answer different briefs
The local mobile app supplier base leans independent and small, with a strong design culture and a real open source engineering tradition sitting alongside it. Those are two different kinds of firm and they are good at different things. A design led team will improve what your product is and how it feels, and will usually need a clear technical counterpart for anything complex behind the screens. An engineering led team will handle integration, data and scale, and will produce a serviceable interface that is rarely distinctive.
Decide which risk you have before you shortlist. If your differentiation is the experience, buy design and hire engineering support around it. If your differentiation is what the system does, buy engineering and commission the interface separately. Asking one small studio to be excellent at both is the most common way a modest budget produces something mediocre in both directions.
Being found in the store is its own discipline
People discover a mobile app through search inside the stores, through your own channels, and through word of mouth, and the listing is the only part of that you fully control. The title, subtitle, keyword field, screenshots and the first two lines of the description do most of the work, and screenshots in particular are often treated as an afterthought when they are the main sales asset.
Put listing work in the scope with a named owner, and agree who updates it when the product changes. Ask each candidate whether they have run an experiment on store assets and what moved. This is also the moment to be clear with yourself about acquisition: an installed product does not market itself, and the budget to make anyone aware of it is separate from the budget to build it.
What a mobile app costs after the launch invoice
Both platforms ship a major operating system release every year, store policies change, certificates expire and dependencies you never chose go unmaintained. A product left alone for twelve months will fail its next submission for reasons that have nothing to do with your roadmap.
Price maintenance separately and write down what it covers: crash monitoring and response time, store rejections, annual platform updates, and who can build and release if the original engineer leaves. Register the App Store and Play Console accounts, signing keys and push credentials to your own organisation with the studio added as a collaborator, and keep the repository and build configuration under your control. That arrangement costs an afternoon at the start and is what makes changing supplier a choice rather than a rebuild.
Running a comparable tender among Portland studios
Brief three mobile app firms with the same short document: what the product does that your site cannot, who uses it and how often, what it integrates with, what data it touches, and what retention would make it worth keeping. Then read their assumptions, exclusions and questions before any figures, because a gap between two totals is almost always a gap in scope rather than in greed.
Take references from whoever ran the product a year after launch rather than from the person who signed. Keep adjacent work as separate tenders with search specialists in this market, local motion and animation studios or communications support for the launch. For skills the local bench does not cover, the wider pool including Seattle works in the same hours, and the full picture is in the mobile application development directory. When the brief and the success measure are written down, send it to several verified studios at once.