Let’s talk
← All case studies004
ConstructionCustom software · Micro-SaaSUnited Arab Emirates

A document management system in 15 business days

Scattered files and incompatible workflows replaced with a custom system built around the practices that already existed — not a platform migration nobody would adopt.

15 daysBrief to working systembusiness days, deployed
8×Faster document retrievalmeasured after go-live
20%Project management efficiencyimprovement reported
0Training programmes requiredbuilt for intuitive adoption
Engagement15 business days, brief to working system
Period2026
ScopeCustom software development · No-code development · Bubble.io · Micro-SaaS platform · Cloud storage integration
The short version

Gulf Erection Constructions was losing time to scattered documents and workflows that did not talk to each other. I built a custom document management system and deployed it in fifteen business days — designed to integrate with the practices the team already had rather than replace them, so that adoption did not require a training programme.

The problem01 / 03

The files existed. Finding them was the job.

Documents were scattered across storage nobody had agreed on, and the processes around them had grown incompatible with each other. On a construction project that is not an inconvenience — it is hours a week, repeated by everyone, on work that produces nothing.

The standard answer is a document management platform. The standard outcome is that a team keeps using the folders it already trusts, because the new system asks them to work differently on the day they are busiest.

The build02 / 03

Built around the existing practice, not against it

The system was built to fit the way this team already filed and retrieved things, and to integrate with the cloud storage they already used, rather than demanding a wholesale migration before it delivered any value.

It was built no-code, on Bubble, deliberately: for a scoped internal tool with a known workflow, that route puts a working system in front of the people who need it in weeks rather than quarters — and leaves it editable by someone other than its author.

  • Integrated, not replacingExisting cloud storage and existing filing habits were carried into the system rather than deprecated by it.
  • Scoped for adoptionDesigned so that minimal training was required — the measure of success was people actually using it, not feature count.
  • Delivered as a micro-SaaSA contained platform with its own access model, rather than a script or a spreadsheet with ambitions.
A tool nobody adopts has a feature list and no users. The constraint here was adoption, so adoption is what the design optimised for.
The outcome03 / 03

Eight times faster retrieval, and a fifth off the management overhead

Document retrieval came out eight times faster, and project management efficiency improved by twenty per cent — on a system that was live fifteen business days after the brief.

What this engagement proves(03)
  1. 01

    The constraint is usually adoption, not capability

    Building around the practices a team already trusts is what makes a system get used. The version that requires everyone to change on day one is the version that quietly gets bypassed.

  2. 02

    No-code is a delivery decision, not a compromise

    For a scoped internal tool with a known workflow, it puts a working system in front of users in weeks and leaves it maintainable by someone other than the person who built it.

  3. 03

    Fifteen days is a process outcome

    The speed came from scoping the workflow properly before building, not from cutting the parts that make a system usable.

A working document management system in fifteen business days — eight times faster retrieval, twenty per cent better project management overhead, and no training programme required to get there.

Next case studyCraft quality, matched by the digital presence.Custom Joinery & Renovation · Sydney, Australia
Hari Prasad Yarragolla

Recognise anyof this?

Prefer email? Write to yarragollahari@gmail.com directly.

Let’s talk.

Tell me what you are building — a storefront, a site, an internal tool, or the systems and agents behind them. I will tell you what I would build first.

  • Quick response.You will hear back from me — not an account manager reading a script.
  • A sitemap and a mockup.You see the real structure and design of what you are commissioning, before any money changes hands.
  • Clear next steps.A scope, an order of work, and an honest view of what it is worth — including if the answer is that you do not need a rebuild.
Hari Prasad Yarragollayarragollahari@gmail.com+91 83418 86288
Website developmentCustom Shopify developmentShopify LiquidNext.js buildsE-commerce developmentAPIs & endpointsSystems integrationInternal tools & micro-SaaSAWS infrastructureAI automationAI agentsVoice agents