CONTACT STRUCTURE

Use the right lane from the start.

A premium site feels better when each kind of inquiry goes into the right path: packaged product questions, custom project intake, or direct founder contact.

LANES

Best way to contact

Product questions

Use product pages and official MQL5 listings first, then Telegram if the workflow question still needs clarification.

Custom projects

Use the brief builder on the custom-development page, then continue on Telegram with a cleaner first message.

Direct founder trust

Keep the public MQL5 trail visible for buyers who want to verify the person behind the work.

MESSAGE QUALITY

What to include in a first message

  • Platform: MT4, MT5, or both.
  • What already exists: product, codebase, workflow, screenshots, or nothing yet.
  • What must happen: the exact behaviour you need, not only the broad idea.
  • Constraints: symbol rules, account type, VPS setup, broker quirks, or outside integrations.
  • Outcome: what counts as done, accepted, or useful.
DIRECT CHANNELS

Direct channels

Telegram

Best for fast back-and-forth after the request is already structured.

MQL5 profile

Best for public trust and packaged product verification.

Email

Best for documents, screenshots, or a more formal first message.

FAQ

Simple answers for the two-lane model

Why not buy custom services directly on the website?

Because the custom lane is not a fixed-scope e-commerce product. The site should qualify the request first, then move the real scoping work to direct conversation.

Why keep MQL5 in the flow?

Because it already provides the official listing, public reviews, and the purchase/activation path for packaged products.

Why list every product on the site?

Because search visibility and comparison improve when the whole catalog is indexed under a cleaner information architecture.