The technical side
PhonedTech builds software with proven, widely used tools. Every change goes through code review and automated tests before it ships, and what runs in production is monitored. At handover, your team gets the full code repository, documentation, written decision records and a list of every account and access. This page is written for developers and CTOs.
How we build
We build with widely used, well-documented tools that your next developer already knows. Something new has to earn its place in your project.
One well-chosen database and a background queue go a long way. We split a system into more services only when there is a clear reason, because every extra part has to be run and looked after.
The code repository, the cloud account, the domain and the keys are in your company's name from the start. We work with our own access, which you can switch off at any time.
Work goes live in small pieces. Each change is tried on a test copy (staging) first and can be rolled back, so a release is routine, not an event.
Every important decision gets a short written record: the context, the options and why we chose one. Whoever works on the system next doesn't have to guess.
Passwords and API keys live in a secure vault, separate from the code, and each person and each service gets only the access it really needs.
The stack
The tools we reach for most often, and when. We choose for each project: if your team already runs on something solid, we usually build on it rather than replace it.
For everything users actually touch.
Servers, services, business logic.
Where your data is stored and kept consistent.
Where it runs and how we know it's healthy.
AI models that run inside live products.
Less manual work in inboxes, spreadsheets and copy-paste.
Tools that show us what's happening and alert us only when something needs attention.
Defaults that prevent the obvious mistakes.
When you don't need to build it from scratch.
Quality
Every change goes through a pull request with a short note on what changed and why. Automated checks run first, then another engineer reviews the code before it's merged. Reviews catch bugs, and they also spread knowledge, so no part of your system lives in one person's head.
Tests are written with the code, not after it. They run on every pull request and again before each release, and every change is tried on a staging copy before it reaches your users.
Once it's live, we keep watching it. Errors are reported with the details needed to fix them, uptime is checked around the clock, and logs are kept so we can see what happened. Alerts go out only for real problems, so nobody learns to ignore them.
Handover
At handover, or whenever you ask, your team gets everything it needs to run the system and change it without us.
The full repository with its whole history, in your organization's account on GitHub, GitLab or Bitbucket, including the build and deployment setup.
A README that gets a new developer running locally, an overview of how the parts fit together, how to deploy, and short guides for the things that can go wrong.
The important decisions in writing: the context, the options we weighed and why we chose one.
Every account, service, domain and key the system depends on, who holds access to each and how to change it. When you're ready, we hand everything over and remove our own access.
Working with your team
Already have developers? We can work inside your setup rather than next to it: your repository, your issue tracker, your chat and your code style.
How we work together depends on you and the project: a fixed-price project, a monthly retainer, a part-time CTO, a dedicated team, or white-label work for agencies.
From our guides
Longer pieces on how and why we build the way we do.
Choosing a cloud provider for your website, app or business system? How AWS, Azure and Google Cloud differ, what drives the bill, and how to choose.
Hosting & upkeep · 6 min readYour website or app is live and customers depend on it. Here is our 8-week plan for safe updates, clear alerts and tested backups, and what drives the running costs.
Software products · 5 min readShould all your customers share one system, or should each one get their own? Here are the three real options, what each costs you, and how to choose.
How it's built · 5 min readMost businesses don't need a bigger, more complex system for their behind-the-scenes work. When simple is enough, the signs it isn't, and how to switch safely.
How we work · 5 min readEvery big decision on your project gets one plain page: what we chose, what else we considered, and why. A few minutes that save long arguments later.
Bring them to a free 30-minute call with an engineer, or send them on WhatsApp or by email. One of our engineers reads every message and usually replies within one business day.
