When does a custom system make sense?
It makes sense when the process is what sets your company apart, when packaged software needs side spreadsheets to work, or when per-user licences exceed the development cost over two or three years. In those cases a system built for your flow cuts rework and gives you back control of your data.
It does not make sense when a mature product solves 90% of the need at low cost. JBKR says so during the assessment: we have recommended WordPress, WooCommerce or a ready SaaS whenever that was the best answer for the client.
What has JBKR Web already built?
An ERP in production since 2009, with electronic invoices over web services, ticketing and a Banco do Brasil integration, maintained and evolved to this day. An education management system for the City of Curitiba (Java Web and Oracle, through ICI). A PHP intranet with a product configurator and API integration, a marketplace MVP in Node.js, Angular and Firebase, an SMM dashboard with Mercado Pago transparent checkout and an audit system replacing manual routines.
The projects are described, with stack and year, in the portfolio. When the client allows it, the name is shown; otherwise, the sector.
How is the project run?
Through the JBKR Method: Discovery (1–2 weeks) to close scope, success metrics and an honest estimate; Proof of concept (2–4 weeks) with the smallest flow that proves the value, on real data; Production, with automated tests, staging, documentation and monitoring; and Continuous operation under the monthly plans.
Deliveries are incremental (every two or three weeks the client sees something working) and the code lives in a repository the client can access from day one. At the end, source code, database, credentials and documentation are yours.
Which technology is used and why?
Three criteria: what your team already operates, what is easiest to maintain over the next five years and what meets the performance and security requirements. In practice: Angular and TypeScript on the front end; Node.js, PHP (Laravel), Java or .NET/C# on the back end; MySQL, SQL Server, Oracle, MongoDB or Firebase for data; SharePoint when the company lives in Microsoft 365.
The foundation is a career that started on the IBM mainframe at HSBC (COBOL, CICS, DB2) and went through Java/Oracle and .NET before Angular and Node. That matters: someone who has maintained systems for 15 years picks technology with the maintainer in mind.
Frequently asked questions
What is custom software development and when is it worth it?
It means building a system around your process instead of bending your company around off-the-shelf software. It pays off when the process is a competitive advantage, when the packaged product needs side spreadsheets to work, or when per-user licences cost more than development over two or three years.
Which technologies does JBKR Web use for custom systems?
Angular and TypeScript on the front end; Node.js, PHP (Laravel), Java and .NET/C# on the back end; MySQL, SQL Server, Oracle, MongoDB and Firebase for data; SharePoint for corporate intranets. The choice follows what your team already runs and what is easiest to maintain for the next years, not the trend of the month.
Do you build ERPs and intranets?
Yes. Since 2009 the founder has maintained and evolved an ERP with Brazilian e-invoicing (NF-e) over web services and a Banco do Brasil bank integration, and JBKR has delivered PHP intranets with a product configurator and API integration, plus SharePoint Online workflows.
How does the process work, from quote to delivery?
The JBKR Method in four steps: Discovery (1–2 weeks, scope and metrics), Proof of concept (2–4 weeks, prototype on real data), Production (tests, telemetry and documentation) and Continuous operation (monthly plans). You get a written proposal before any code is written.
How much does a custom system cost?
It depends on scope: screens, business rules, integrations and user roles. A fixed-scope MVP is contracted as a project with the price set in the proposal. One-off work uses the On-Demand plan (from BRL 250/hour, estimate before the work starts); continuous evolution and support use the monthly plans: Care from BRL 1,125/month and Expert from BRL 2,050/month. Every proposal is written and itemized.
Who owns the system when it is done?
You do. Source code, database, credentials and documentation are handed over at the end of the project. JBKR does not lock clients in through technical dependency: support is optional and contracted through the monthly plans.
