Custom software · Modernization · Accessibility · Phoenix + remote
Work directly with the engineers who build your software.
Progressivity builds and maintains web, cloud, backend, iOS, and macOS software for companies. Harold Davis leads each project and stays involved from the first scoping call through launch. If another engineer joins the work, you will know who they are before the project starts.
01When to call us
Tell us what is getting in the way.
You do not need to arrive with a technical specification. Tell us what your team is trying to do, what is slowing it down, and what has already been tried. We will help decide if the next step is a new build, an integration, or a careful repair.
Build a product or internal tool
Move a proven idea or manual workflow into software your team can run without workarounds.
Update a system that still has to run
Fix the unstable parts first, then replace older pieces in stages while the business keeps using the system.
Connect the systems you already use
Move data between tools, automate repeated steps, and give staff one reliable place to do the work.
Fix accessibility problems
We assess and remediate web, iOS, and macOS applications against WCAG criteria. You get a clear record of what we found and changed.
02Services
Software work we take on.
We can deliver a defined project from start to finish or take responsibility for one part of a larger product.
Custom web applications
Customer portals, internal workflow tools, role-based dashboards, and administrative systems built around the people who use them.
Backend, APIs, and integration
Services and data models that connect payments, identity, mapping, scheduled jobs, and other business systems.
Cloud delivery
Applications on Google Cloud and Firebase with separate environments, repeatable deployments, and a documented operating path.
Native iOS and macOS
Swift, SwiftUI, UIKit, and Objective-C work for field, consumer, enterprise, and accessibility-intensive applications.
Accessibility engineering
Assess existing applications, fix problems, and add checks that catch accessibility regressions before release.
Modernization and sustainment
Take over existing software, update aging dependencies, replace risky pieces, write the missing runbooks, and keep the application current.
03Proof
Nine years building production software.
Harold Davis leads every Progressivity engagement. His professional background includes Apple, Ibotta, DroneDeploy, and U-Haul.
- Professional engineering
- 9 yearsProduction consumer and enterprise software
- Platform experience
- AppleTwo years as a software engineer
- Consumer scale
- IbottaPayments-adjacent flows and service integration
- Enterprise systems
- DroneDeploy + U-HaulField workflows, geospatial data, and logistics
About these names. These companies are part of Harold's employment history. They were not Progressivity clients. Selected work samples and references are available when customer permissions allow.
04How it works
A straightforward delivery process.
We use working demos, documented decisions, and code in your repository to show progress.
Learn
We talk with the people who use or manage the software and review the systems already in place.
Plan
We propose the order of work, milestones, acceptance criteria, dependencies, and known risks.
Build
We demo working increments. Source, tests, and documentation go into your repository as the work proceeds.
Ship
We deploy the software, document how it runs, transfer knowledge, and plan any ongoing support.
05Ways to start
Three practical ways to begin.
Some projects are ready to estimate. Others need a short investigation first. We will recommend an engagement that matches what is known today.
Assessment or recovery plan
Useful for an inherited codebase, accessibility problem, technical decision, or project that needs a closer look before implementation.
Fixed-scope delivery
A good fit for an application, feature, integration, remediation, or modernization step with clear acceptance criteria.
Ongoing engineering and sustainment
For software already in use that needs planned improvements, current dependencies, better documentation, and ongoing attention.
06Fit
When a small senior team works well.
Progressivity works best with customers who can make decisions, give us access to users or operators, and work with us in stages. Work that needs a large bench or round-the-clock support belongs with a different firm.
Good fit
- The project needs senior engineering attention
- Someone on your team can make product decisions
- The work can be delivered in useful stages
- Accessibility, maintainability, and documentation matter
- You want the engineer who scopes the work to stay involved
Probably not a fit
- You need many engineers to start at once
- You need a staffed support desk around the clock
- You are buying open-ended staff augmentation
- The date or budget leaves no room to investigate technical risk
- The work centers on a platform we do not specialize in