Rahul K.

Most clients come in with a working product that needs serious improvement, or an idea that needs to be built from the ground up without constant hand-holding. Both situations are where I operate best. Over the past few years, the work has been across long-running engagements: • An ERP system for a Gulf Coast business, running 400+ hours over an extended period • An AI-powered SaaS platform for book publishing, developed and iterated over 200+ hours • A full stack engagement where the client rated the work 5.0 and kept extending None of these were quick in-and-out jobs. Each required understanding the client's actual business problem, not just the feature list, and making decisions independently when requirements were unclear. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗲 𝘄𝗼𝗿𝗸 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗶𝗻𝘃𝗼𝗹𝘃𝗲𝘀: • Full stack development across React, Node.js, and cloud infrastructure • Business Central integration and ERP module development • AI feature development inside web-based SaaS products • Database design, API development, and deployment setup • Picking up existing codebases and improving them without needing a full rewrite explanation 𝗛𝗼𝘄 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘁𝘆𝗽𝗶𝗰𝗮𝗹𝗹𝘆 𝗿𝘂𝗻: • First week: understand the codebase, identify the real blockers • Communication is async-first. Updates come when there is something worth updating • If a requirement is unclear or risky, it gets flagged before work starts, not after • Decisions get documented so future developers are not starting from zero 𝗪𝗵𝗮𝘁 𝘄𝗼𝗿𝗸𝘀 𝘄𝗲𝗹𝗹 𝘄𝗶𝘁𝗵 𝗺𝗲: Long-term product work. If a project needs someone who joins for three weeks and disappears, that is not the right fit. The strongest results have come from engagements where trust built over time and the work compounded. Short-term projects work too, but only when the scope is clear and the client knows what they need. Vague requirements with tight deadlines rarely end well for either side. 𝗖𝘂𝗿𝗿𝗲𝗻𝘁 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Open to new contracts. Preference for product-focused work with real technical depth.