MODRACXKENNETH D'SILVA

Contact

Let's talk about the build, the redesign, or the system behind it.

Open to freelance work, contract builds, retained support, and team collaboration where strong delivery and practical thinking matter.

Best fit

Good projects usually need one of these

  • A stronger ecommerce presence, or a redesign with clearer conversion paths
  • A CMS site that needs to feel more premium, structured, and rankable
  • An ERP, IMS, HRM, or internal workflow needing better logic and usability
  • Search, security, performance, migrations, or ongoing technical support

Project brief

Share the essentials and this becomes an email draft.

Nothing is sent from this page. Submitting opens your own mail app with the details filled in.

Open mail app

Before you send

Starting an ecommerce project: what happens next.

Practical answers about working together, so the first email does not have to be a guess.

What happens after I send a brief?

You get a reply with an honest read on the problem: whether it is the ecommerce build, the platform choice, the data model, or something operational that a website will not fix. If it is a fit, that leads into scope, approach, and a delivery path. If it is not, I will say so and point you somewhere more useful rather than stretch the work to fit.

What should the first message include?

The current situation, what platform you are on, what is going wrong or needs building, any deadline that is real, and whatever already exists — a live URL, a repository, a half-finished design, or a document. Rough is fine. A messy description of the actual problem is more useful than a tidy specification of the wrong one.

What kinds of projects are the best fit?

Magento 2 and Shopify builds, redesigns, and migrations; CMS and marketing sites that need to feel more premium and rank better; ERP, IMS, HRM, and internal tools that need clearer logic and usability; and search, security, performance, or ongoing technical support on systems that already exist.

Do you work fixed-scope or on retainer?

Both. Defined project builds where the scope can be pinned down, and retained support where the work needs continuity — patching, optimisation, incremental feature delivery, and being available when production misbehaves. Contract work and collaboration inside an existing team both work too.

Do you take on small jobs?

Yes, if they are well-defined — a performance pass, a security and patching review, a schema and technical SEO fix, a stubborn checkout bug. Small work is often how a longer engagement starts, and it is a low-risk way to find out whether we work well together.

Where are you based, and does time zone matter?

Ahmedabad, India (IST), working with clients worldwide in English. In practice that means a solid overlap with Europe, Asia-Pacific, and the Middle East, and early-morning overlap with the Americas. Asynchronous written updates carry most of the communication, so the gap rarely becomes the bottleneck.

Does the form on this page send my details anywhere?

No. The project brief form runs entirely in your browser — submitting it opens a draft in your own mail app with the details filled in, which you then send yourself. Nothing is transmitted to this site or to any third party from that form.

Need clarity first?

Start with the messy version. I'll help shape the next step.