# Custom software development, by a product team. > TechFabric builds custom software as product development: web applications, mobile apps, customer portals and internal tools that work with the systems your business already runs on, such as Business Central or Salesforce, with engineering, product and design in one team. The people who scope the work build it and stay through go-live. 115+ engineers across four offices, averaging fifteen years each. Canonical: https://www.techfabric.com/software --- Most of what goes wrong in a software project happens before anyone writes code, in the gap between the person who understood the problem and the team handed a specification. We close that gap by not creating it. Athlinks stitched 400M+ athlete records together this way, SWBC doubled the orders its platform processes, and orders placed on AmTab's web store reach Business Central without anyone re-keying them. ## Pages - [Ecommerce development](https://www.techfabric.com/software/ecommerce): We build commerce systems and the operational stack they depend on: the storefront, the catalogue, and the integration to the ERP, the CRM and the warehouse that have to agree with it. Most of this work is B2B, where the order is the start of a process rather than the end of one. - [Web application development](https://www.techfabric.com/software/web): We build web applications that people use as their job: operator consoles, internal platforms, customer portals and multi-tenant products. Built with the admin surface, the audit trail and the deployment path treated as part of the product rather than as things to add once it is live. - [Mobile app development](https://www.techfabric.com/software/mobile): You know your users and roughly what the app has to do. We design and build it for iOS and Android with the backend underneath, handle the store submission and the release, and set it up so whoever owns it in year two can keep shipping, which is where most mobile projects quietly fail. ## Common questions ### What is custom software development? Building software for one organisation's problem rather than configuring something built for a market. It is worth doing where the process is genuinely yours and a packaged product would mean changing how you work to suit it, and it is usually not worth doing where a well-supported product already fits. We will tell you which one you are looking at. ### Is custom software development the same as product development? For us, yes, and the second name is the more accurate one. A custom build that gets treated as a specification to implement produces software nobody wanted; the same work run as product development has engineering, product and design deciding together and adjusting as they learn. That is the service at /services/platform, and this page is the front door to it. ### What have you built? A sports platform for BZZR where live games, creator content and podcasts sit under team and talent control. A pipeline for Athlinks stitching more than 400 million athlete records together across disparate sources. A rebuilt LOSExpress for SWBC that doubled the orders it processes. All three have case studies at /case-studies. ### How much does custom software cost? It depends on scope, and any number offered before a scope exists is a sales tactic. What we can commit to is that scoping is a short paid piece of work with a written output, so the estimate that follows is against something specific rather than a wish. Small first engagements are normal and often how a longer one starts. ### Do you work with our existing team? Usually, yes, and it is the shape we do best. Our engineers work in your repository, in your process, alongside your people. Where you have no engineering team yet we will bring the whole one, product and design included. ### Who owns the code? You do, all of it. Where one of our open-source accelerators is involved we say so explicitly and in writing, including what it means for you to keep running it after we leave. They are Apache-2.0 and deployed into your own accounts, so there is nothing to be locked into. ### What technologies do you build on? TypeScript and .NET for most application work, Python where the data and model work lives, on Azure, AWS, Google Cloud and Cloudflare. Databricks where the product belongs next to the lakehouse, and Temporal under operations that must not half-complete. The stack follows the problem rather than a house preference. ### Do you take small projects? Yes. A design system, a component library, one integration or a single service is a legitimate piece of work and often how a longer engagement starts. What we do best is a product where design, product and engineering sit in one team, so that is what we will suggest when it fits. It is not a condition of working with us.