Tecknomancy

Realm of Tecknomancy

Present your request clearly. This form helps define project type, system requirements, service model, and scope before review.

Project Requests Scope Review Service Clarity

← Back to Map

Request Intake

Open

The form captures project type, system requirements, and scope before review.

Contact Route

Direct

Direct contact route for project requests, scope review, and service discussion.

Review Flow

Structured

Each section helps clarify the project before final submission.

Project Request Form

Direct intake

Submitting this form does not create a contract. It begins a review. Final scope, pricing, service model, and approval are confirmed directly by Tecknomancy after the request is reviewed.

Form Progress

Complete the first section

Contact

Requirements

Service Model

Summary

Section 1

Contact Details

Provide your contact details, project type, budget range, and preferred timeline.

Name

Project Type

Budget Range

Preferred Deadline

Section 2

System Requirements

Define what the project needs to do and which system structure fits best.

What should this system actually do

Which description fits closest

Do different parts of the system need to communicate with each other

Section 3

Service Model

Confirm your understanding of service model, scope, and feature changes.

What do you believe you need

How do you understand the service model

If you ask for more features later, what do you expect

Do you understand that managed hosted systems remain under Tecknomancy control and are not sold into client ownership

Do you understand that anything outside the agreed scope may be quoted separately

Section 4

Project Summary

Provide a clear summary of the work required.

Project Summary

Final Review

If the information is complete, submit the request for review.

Contact Options

Direct routes

WhatsApp Contact

If you prefer direct contact, use WhatsApp to discuss your project in real time.

Speak via WhatsApp

What this form asks for

State the type of work you need, what it should do, and whether it is a managed service, standalone project, marketplace, trade centre structure, or connected system.

Clear project definition comes before pricing.

Why these questions exist

Clear answers protect both sides. They define scope early, reduce misunderstandings, and prevent vague expectations before any agreement begins.

Clear scope protects the project.