Question 1

Who is CAM Software?

Accepted Answer

CAM Software LLC is a founder-operated mobile app development agency based in Northwest Arkansas. Chris Martinez (founder) runs every engagement. The agency is organized around four productized pillars: Audit, Build, Rescue, and Partner. We work in English and Spanish.

Question 2

Do you only build the mobile app, or the whole product?

Accepted Answer

The whole product, with mobile as the spearhead. We build the API, database, auth, and cloud infrastructure the app runs on, plus any companion web surface (admin portal, user dashboard, marketing site) that needs to stay in parity with the app. Chris is senior on the web side too (Next.js, React, Tailwind, Supabase, AWS; this site is on Next.js). What we don't take is standalone website work with no product behind it. If that's what you need, we'll point you to a shop that specializes.

Question 3

Does Chris actually work on the code, or does he just review?

Accepted Answer

Chris is hands-on the build. He reviews every PR, owns the architecture decisions, and personally touches the release process. If a contractor comes in for specific depth (heavy animation, specialized native work), Chris still signs what ships.

Question 4

What makes you different from a generalist agency?

Accepted Answer

We are mobile-led and founder-operated. Every engagement is led by Chris, who ships his own apps in the same stores our clients use. Generalists optimize for capacity across services; we optimize for depth: the mobile app first, plus the backend and web surfaces the product needs. Each pillar (Audit, Build, Rescue, Partner) is priced and scoped on its own. You can engage one pillar and stop there, or chain them. Rescue, then Partner is the most common path.

Question 5

What does the Technical Audit actually include?

Accepted Answer

The audit answers two questions: do users understand how to use this app, and are they happy using it? A 3-second delay is enough to frustrate a real user. That's the bar. So we look for security vulnerabilities, scalability headroom, reusable vs brittle code, the full user-flow review (happy path and the unhappy paths where things quietly break), accidental regressions, and every place we can make the app more efficient. You get a written report with severity-ranked findings, prioritized 30 / 60 / 90-day recommendations, and a live walkthrough call.

Question 6

Do you need access to our repo?

Accepted Answer

Yes, read-only. An audit can't verify HIPAA §164.312 safeguards, build pipelines, or security controls from a compiled build alone. NDA provided, BAA signed on request for HIPAA contexts. Access is removed immediately after delivery with a tear-down confirmation email.

Question 7

Does the wearable add-on cover both Apple Watch and Galaxy Watch?

Accepted Answer

Either one, or both if your app ships both surfaces. We review complications, companion pairing, battery impact, and HealthKit / Health Connect integration.

Question 8

How do you choose React Native vs native?

Accepted Answer

React Native is the default: fastest path to both stores with a small team. We argue for native Swift or Kotlin when the app needs hardware-specific APIs at depth, performance demands it, or the post-launch team already knows native. The recommendation is in your Build proposal with a one-paragraph justification.

Question 9

What happens if the timeline slips?

Accepted Answer

Milestones are flat-fee. Timeline only slips if you change scope, and that's priced as a change order. If the slip is on us, you don't pay more.

Question 10

Who owns the code at the end of a Build?

Accepted Answer

You do, entirely. Every commit goes to your repo, your App Store Connect, your Play Console. We don't hold ownership as leverage. At handoff you have a clean repo, a green pipeline, and a runbook.

Question 11

Why is a paid Technical Audit mandatory before a Rescue?

Accepted Answer

Because rescue quotes without an audit are guesses. The audit surfaces what's actually broken (which is almost never what the team thinks) so we can quote the rescue honestly as a flat fee. The audit is a standalone product. You walk away with a PDF and a plan whether or not you move forward with a rescue.

Question 12

What if the app turns out to need a rebuild, not a rescue?

Accepted Answer

The audit will say so. We'll rescope as a Build (full rebuild) or a Partner (stabilization + roadmap), never stretched as a Rescue. The audit's PDF and plan go with you regardless of which engagement comes next.

Question 13

What does "stable" mean at handoff?

Accepted Answer

Three things: the app is reliably crash-free in real user sessions, the build pipeline runs cleanly from commit to App Store / Play Store submission, and there's a runbook so the next team can ship a release without calling us.

Question 14

Why don't you call it "fractional CTO"?

Accepted Answer

Because the label doesn't add clarity. It adds a buzzword. The two Partner tiers say exactly what they do: "Embedded team" and "Embedded mobile leadership." The word "Partner" carries the brand; the subheadline carries the tier. The role is still a fractional CTO in practice for the leadership tier, just without forcing the term onto the page.

Question 15

What does the 3-month minimum mean?

Accepted Answer

You commit to 3 months of the monthly retainer at the tier rate. After that, month-to-month with 30 days notice. Longer commitments get a discount: 6-month = 5% off + a Quick Scan audit at month 3; 12-month = 10% off + Quick Scan + Full Audit + quarterly architecture review.

Question 16

Can I switch tiers mid-engagement?

Accepted Answer

Yes. Up at any time (pro-rated). Down at the end of your current commitment with 30 days notice. We won't trap you in a tier that stopped fitting.

Question 17

Do you use AI to build our app?

Accepted Answer

Yes, as a delivery tool, the same way we use a debugger or a CI pipeline. Chris builds custom agents and MCP servers (Model Context Protocol) and uses agentic tools to raise quality and speed. Every change is read and understood before it merges, and Chris signs what ships. AI is how we deliver faster, and for teams that want this tooling in their own workflow, we also build it as a standalone, fixed-fee engagement.

Question 18

Can you help our team use AI, not just the developers?

Accepted Answer

Inside an embedded engagement, yes. That has meant agents that check every pull request for accessibility, security, reusability, and test coverage before merge; faster QA turnaround with clear suggestions when something fails; and giving product managers and product owners clear visibility into ticket quality (where work bounces back and why). The whole team moves faster, not only the engineers.

Question 19

What languages do you work in?

Accepted Answer

English and Spanish, for both the website and the working conversations. Chris is fluent in both.

Question 20

Do you work with healthcare / HIPAA-covered entities?

Accepted Answer

Yes, about five years of HIPAA-context mobile delivery across ABA therapy, e-prescribing, and EHR work. We sign BAAs. Healthcare is case-study proof, not our positioning. We're a mobile agency first.

Question 21

What if you're not the right fit?

Accepted Answer

We'll say so when we talk and try to point you to a better shop.

FAQ

About the agency