The Codemen field guide

The practical questions, answered.

Understand how products, projects, payment and delivery work before choosing your next step with Codemen.

Discuss your requirements
/01

Two ways to begin

Browse a source product when you want to evaluate an existing foundation, or start a project conversation when your requirements need a tailored scope. Many projects combine both approaches. The useful starting point is a short description of the people using the product, the actions they need to complete and any existing systems that must connect.

/02

Keep the decision connected to the details

The product page, selected license and agreed project scope answer different questions. Review all three where relevant: what the software includes, how it may be used and which additional work will be delivered. For an order already placed, your account is the place to follow payment and delivery status and keep support connected to the order reference.

Clarity before commitment

Questions worth asking.

What does Codemen build?

Our service scope covers cryptocurrency platforms, wallets and payments, blockchain applications, AI workflows, web and mobile software, design and operational infrastructure. The service directory explains individual capabilities; each project receives an agreed scope rather than an assumption that every capability is included.

Can I see a product before buying?

Use the demo link where one is published, or request a demonstration from the product page. Include the workflows you want to review so the discussion can address the fit, integrations and expected handover.

How do I track a purchased source product?

Sign in to the account used for checkout and open your orders. Payment and source delivery have separate statuses. Keep the order reference when opening a support ticket so the team can find the correct purchase.

What does manual delivery mean?

After payment is confirmed, the team prepares the agreed source handover and records delivery against the order. The delivery method and any additional setup work should be confirmed from the product or order scope; manual delivery does not imply immediate installation on your server.

Which payment network should I use?

Use only the asset, network, receiving address and amount displayed on your active invoice. Availability can change with configuration. If the details do not match your wallet or a payment is unclear, contact support with the order reference before sending another transfer.

Can you adapt or modernize our existing application?

Yes, subject to a review of the code, deployment and rights to modify it. We identify the workflows to preserve, the technical constraints and a migration approach before proposing changes. Share a description first; access can be arranged for a focused review.

How are cost and timeline determined?

Catalog source products display their available license prices. Custom work depends on scope, integrations, existing material, acceptance requirements and responsibilities. We discuss these dependencies before an estimate; a generic feature list alone is not enough to make a reliable commitment.

Who owns hosting and third-party accounts?

The engagement must identify the owner of each hosting environment, provider account and production credential. If setup or management is included, its boundaries are written into the scope. Source delivery by itself does not include external subscriptions or an ongoing managed service.

Connect the next pieces.

Go deeper into the services and software foundations relevant to this conversation.

Let’s define the next step

Tell us what needs to work.

Bring your idea, your current platform or a workflow that needs a better answer. We will start with the right questions.

Discuss your project