The questions people actually ask.

Small enough that you deal directly with the people doing the work, and we would rather say that than imply we are something we are not. We have a team, and we bring in specialists per project where a piece of work needs depth we do not carry permanently. It also means we turn down work we cannot staff properly, and we will tell you that on the first call rather than three weeks in.

A short call, at no cost, about where your operation actually loses time. Often that conversation ends with a recommendation to do less than you were planning, or to fix a process before building anything. If a fuller answer is needed, the AI and Automation Roadmap Sprint produces a costed, sequenced plan you own outright.

Yes. The work is largely remote and we have delivered for clients elsewhere in South Africa. Our operating office is in Randburg, Johannesburg, and we can meet in person in Gauteng where that helps.

Small and medium businesses where a system is genuinely load-bearing: an operation running on spreadsheets, a process that only works because one person remembers it, or software that has outgrown a package. Very large enterprises usually need a supplier who can field a bench, which we cannot.

Often, yes, and it is a large part of what we do. The first step is an honest assessment of what is there. Sometimes the answer is that the existing system is fine and needs maintaining rather than replacing, and we would rather tell you that than sell a rewrite.

Because any number we published would be wrong for most readers. Consulting scope varies enormously, and a price list would either be so wide as to be useless or so specific as to be misleading. Scope and fees are agreed in writing per engagement, after a conversation, and we do not start work without that in place.

It depends on the shape of the work. Fixed scope for an assessment, project-based for a defined build, or a monthly retained arrangement for ongoing work. We favour fixed pricing wherever we honestly can, even on work that might run long, because that puts the risk of a wrong estimate on us rather than on you. Hourly billing has its place too, usually once we have worked together before and both sides know how the other operates. Whichever model applies to your engagement is set out in writing before anything starts, including what is not included.

No, and the work is deliberately built so you are not. You own the source code and the data. Everything is documented, tested and deployable by another engineer. If we are still working together in a year it should be because you chose it, not because leaving is expensive.

No. Invoices are settled by bank transfer directly with your own bank. This website does not collect or store card details.

On the back end, Java with Spring Boot, Python with Django or FastAPI, Node.js, .NET and C#, or Go, depending on the problem and on what your team can maintain. React and TypeScript on the front, PostgreSQL underneath, AWS or Azure with Terraform describing the infrastructure. For mobile it is Kotlin on Android, Swift on iOS, and Flutter or React Native where cross-platform is the better trade-off. Python where data work and AI are central, Go where a service should start instantly and stay small, .NET where a business already runs on Microsoft. What does not change is that we pick things you could hire someone else to maintain in five years.

That is the standard we build to. Documentation, automated tests, a working local setup and a deployment pipeline are part of delivery rather than extras. The Samloryx platform page describes the same approach applied to our own systems.

Where it earns its place, and not where it does not. The assistant on this site answers visitor questions from a knowledge file we control. In client work, AI is used when it solves a real problem better than ordinary software would. A great deal of what gets sold as AI is a scheduled job with better marketing, and we will tell you when that is the case.

Yes. We build native apps in Kotlin for Android and Swift for iOS, and cross-platform apps in Flutter where one codebase on both platforms is the better trade-off. Which of those suits you depends on what the app has to do: heavy device integration usually argues for native, while a straightforward product app on both platforms is often better served by Flutter. We will tell you which we think fits and why.

Ask what the app needs from the device. If it needs the camera, offline use, push notifications, background location or payment hardware, an app earns its place. If it is mostly screens and forms, a well-built web application will reach more people with no install, no app store review and one thing to maintain. Plenty of businesses are talked into an app when a good mobile web experience would have done more for less.

Yes. Samloryx Consultancy (Pty) Ltd, CIPC registration 2022/231776/07, a 100% Black-owned South African private company founded in 2022. Full details are on the legal page.

Not yet, and we will not imply otherwise with a wall of logos. The founder holds the Microsoft Certified: Azure Solutions Architect Expert certification (AZ-305), which is a personal certification and a different thing from company partner accreditation. When Samloryx genuinely holds partner status, the partners page will name it.

No. Some tenders and enterprise procurement processes require one, and where that is the case we will tell you at the start rather than at the end. The security page sets out what we actually do to protect information.

We collect the minimum needed to reply to you, we do not sell it, and we say who processes it on our behalf. The privacy policy covers general use of this site, and there is a separate recruitment privacy notice for details submitted through the careers page.

No, and the page says so. They reflect the founder's prior employment and consulting experience. They are not Samloryx clients, partners or endorsements. Actual delivered client work is on the case studies page.