Skip to content

Who you are hiring

A software practice in Sukabumi, West Java. Eight documented projects since 2017, each with a written case study on this site.

About Qadr Tech

Software built by the person who answers your email

Qadr Tech Solutions is a software and web development practice in Sukabumi, West Java. It is run by one developer, which means the person who scopes your project is the person who writes the code, and the person who replies when something breaks.

Most of the work here is internal systems for a university: quality audits, lecturer workload, thesis supervision, and the public sites around them. These are systems staff open every working day, not campaigns that end at launch.

  • Custom web application development
  • Internal systems for institutions
  • Website design and development
  • Maintenance for the systems we deliver
The AMI LPM UMMI internal audit system, showing its audit dashboard
AMI LPM UMMI, an internal quality-audit system in production at ami.ummi.ac.id

What the record actually shows

Every figure below can be checked against the project pages on this site. There are no satisfaction rates or delivery percentages here, because nothing measures them.

First documented project
July 2017An internal quality-audit system for Lembaga Penjaminan Mutu UMMI, still listed among the projects on this site.
Documented projects
EightEach one has a written case study here, with the screenshots that go with it.
Built for one university
SevenSeven of those eight serve different units within Universitas Muhammadiyah Sukabumi.

One institution returning across different units, over several years, is the strongest evidence available here. It is also the honest limit of it. This is deep experience in higher education, not broad experience across many industries.

How a project runs

Four steps, the same every time, so you know what happens after you send the first message.

  1. 01

    Conversation

    You describe the problem by email or WhatsApp. If it is not something I can build well, I say so at this point rather than later.

  2. 02

    Scope and estimate

    We agree on what the first working version contains, what it deliberately leaves out, and what it costs.

  3. 03

    Build in the open

    You see working software while it is being built, not only at handover. Changes are far cheaper at this stage.

  4. 04

    Handover and upkeep

    You receive the running system and its source. Maintenance continues by agreement, during working hours.

The person you will be working with

There is no account manager between you and the work.

Gun Gun Priatna

Gun Gun Priatna

Founder and developer

I build and maintain web systems for institutions in Sukabumi, mostly internal tools that staff use every working day.

I handle the whole path from scoping to deployment. That is also why the project list on this site is deliberately short: I take on work I can finish properly and keep supporting afterwards.

Want to talk it through?

Tell me what you are trying to build, and I will tell you honestly whether I am the right person for it.

Let's talk