ENIGMA / FAQS
A little clarity.A better next step.
Find answers about how we work, then contact us with the details of your own project.
Clear scope.
Connected work.
What does your agency do?
Enigma connects marketing, websites and business systems. That can mean a customer-facing store, an ERP and CRM workflow, or managed hosting behind an application. Start with the task that is failing today, such as duplicated stock records or enquiries that nobody follows up, so the proposed work addresses a defined problem.
Who do you typically work with?
We work with independent sellers, growing companies and larger organisations. The starting brief matters more than company size: who uses the system, which locations or channels are involved, what must stay in place and who can approve decisions? Those details help separate an achievable first phase from later requirements.
Are you a full-service creative agency?
Creative and technical work can be scoped together, including identity, website design, development and marketing. A full-service engagement does not mean every possible deliverable is included. The written scope should identify the assets, channels, integrations and ongoing responsibilities before work begins.
Do you work with international clients?
Yes. Share your location, working hours and the markets you serve. Discovery should cover currency, language, tax and privacy requirements, as well as who supplies or reviews local content. Regional requirements and any specialist advice are agreed for the project; one generic configuration does not automatically satisfy every jurisdiction.
What services do you offer?
Our service pages cover websites and e-commerce, ERP Enigma and CRM, Enigma Host, digital and social media marketing, brand identity, video and software engineering. Choose the service closest to your current problem, then review its packages and exclusions. Cross-service requirements should be included in the brief rather than assumed.
Do you offer custom solutions?
Yes, subject to discovery and a written scope. For a custom integration, bring the current application name, available API documentation, sample records without personal data and the workflow you want to connect. We assess access, permissions, dependencies and failure handling before confirming an implementation approach.
Can you handle both design and development?
Yes. Design and development can be delivered within the same engagement. The handover should cover responsive states, form behaviour, content requirements and acceptance criteria, not just a desktop mock-up. For existing systems, discovery also identifies constraints imposed by the platform or the current codebase.
Do you work on one-time projects or ongoing partnerships?
Both are available. A launch project has defined deliverables and an acceptance point. An ongoing engagement needs an agreed service period, recurring work and a review process. Hosting, application support and marketing management are different responsibilities, so confirm which of them your agreement includes.
How do projects usually start?
Send the business goal, current website or software, the main bottleneck, your target timing and any budget constraints. Avoid sending passwords or customer data in the first enquiry. Discovery identifies users, required workflows, existing-system dependencies and a proposed first phase before the final scope is agreed.
How do you communicate during a project?
At the start, agree a primary contact, a communication channel and a review cadence. Keep decisions, approvals and requested changes in a written record. If a decision depends on access, content or another supplier, identify its owner so the project does not wait on an unspecified task.
How long does a typical project take?
A useful timeline depends on the agreed scope, data readiness, integrations and review availability. A brochure website and a multi-location ERP rollout need different plans. Ask for milestones, customer inputs and dependencies in the proposal; a launch date should be confirmed against those conditions rather than a generic promise.
Can the scope change during development?
Yes, through a written change review. Describe the requested behaviour and why it is needed, then assess its effect on cost, timing and already approved work. Approval should happen before the additional work starts. Keeping a later-phase list can protect the current launch from growing without a clear decision.
How do you price your services?
Published packages provide a starting scope. Review inclusions, exclusions, recurring charges and any tax adjustments before configuring a package. Custom work needs a written quotation. A useful comparison includes migration, third-party fees, hosting, support and future changes, not only the initial build price.
Do you offer fixed or hourly pricing?
The commercial model is agreed in the proposal. A defined package and an open-ended integration investigation have different uncertainty. Confirm the deliverables or time allowance, approval process and what happens when additional work is needed; do not assume a particular billing model from a service-page headline.
Is there a minimum project size?
The relevant package page shows available starting options. If your request does not fit a package, describe the smallest outcome that would be useful and ask for a scoped quotation. A smaller first phase may be sensible, but it should still include the access, content and acceptance work needed to deliver it properly.
Do you provide support after launch?
Support depends on the plan and agreement. Before launch, confirm who handles hosting, application updates, backups, access and incident reporting. Ask what is included, what is separately chargeable and how to raise a problem. Keep ownership details and an agreed handover record so support does not depend on one private chat.
LET’S TALK ABOUT YOUR NEXT MOVE
Your goals.
Our next conversation.
Request a free consultationFree initial conversation · No obligation to buy. Share your goals on WhatsApp and request a call time.