Frequently asked questions

WindWeaver can support a broad set of business capabilities: CRM, quotes, invoices, jobs, documents, scheduling, tasks, inventory, purchasing, reporting, portals, integrations, and custom workflows. Most companies should still start with the highest-value workflow first, then expand when the business is ready.

It can replace or connect the messy mix of spreadsheets, inboxes, texts, folders, sticky notes, paper forms, calendars, and disconnected apps that teams use when no single system fits the work.

No. The capabilities are parts of the same managed business system. Some areas are included in the core launch, some are common expansions, and deeper custom work may need a higher plan or scoped build. The goal is to connect the business, not create another pile of disconnected add-ons.

No. WindWeaver starts from a broad business-system foundation and can use trusted extensions or custom development when the business process needs more. The package is defined by the business outcome, not by a fixed technical inventory.

Normal team use means the ordinary people involved in running the company's daily work: owners, office staff, managers, estimators, and field users. Very large teams, franchise-style rollouts, unusual usage, separate companies, or heavy external-user access may need a custom plan.

Usually no. Adding a capability normally starts as a one-time setup and tailoring fee. Monthly care may change only if the added capability increases support load, usage, complexity, outside services, or service-level needs.

Outside services such as payment processors, messaging providers, email providers, accounting tools, domain services, or usage-based platforms may have their own costs. Those are discussed before they become part of the setup.

Core Launch normally covers the lead-to-quote-to-invoice foundation: customer records, lead tracking, follow-up activities, products/services, quotes, sales orders where useful, invoice handoff, users, permissions, basic owner views, and launch training. Jobs, documents, portals, SMS/VoIP, advanced accounting handoff, inventory, deep reporting, and custom engineering are usually focused rollouts or scoped work.

A rollout adds a focused suite area such as jobs, documents, scheduling, reporting, inventory, portals, or integrations. The work is scoped first, launched in a useful phase, then cared for under the managed plan unless it changes the overall support or complexity level.

WindWeaver first looks for the simplest practical configuration: stages, fields, views, permissions, templates, and reports. If that is not enough and the business value is there, custom screens, automations, integrations, portals, or modules can be scoped.

WindWeaver keeps the live system supported, adjusted, and improved so it does not become another tool the business has to maintain alone.

WindWeaver first looks for the simplest practical configuration or trusted extension. If that is not enough and the business value is there, the capability can be custom-built or integrated as a scoped improvement.

Often, yes. Outside tools can sometimes be connected through imports, exports, APIs, forms, email workflows, or practical automation. The right answer depends on the tool, the data, and whether the integration is worth maintaining.

Yes. Field-friendly views can be configured or built for assigned work, notes, photos, status updates, scheduling, and job details when field use is part of the rollout.

WindWeaver can make the operational side of billing and accounting handoff much less manual by connecting quotes, jobs, invoice readiness, payment status, statement imports, reconciliation support, and reporting. It does not replace professional accounting, tax, payroll, CPA, or legal advice.

Yes. WindWeaver can support agreement tracking, contract organization, approval flows, and signed-document workflows where appropriate. Agreement tracking keeps contract details tied to customers, projects, invoices, dates, and internal responsibility. E-signature workflow adds the signing process itself: templates, signer invitations, completed signed PDFs, audit/certificate records, and storage.

For legally binding electronic signature workflows, when configured and used appropriately, the exact approach depends on the document, risk level, legal requirements, and selected signing provider.

DocuSeal can support serious electronic signature workflows, including signed PDFs, templates, audit/certificate records, and automation options. The main differences are usually brand recognition, enterprise compliance expectations, advanced identity features, and who operates the signing system.

For many normal business documents, a properly configured DocuSeal workflow may be enough. Higher-risk, regulated, or special legal documents may require legal review, stronger identity verification, paid provider features, or a different signing provider.

No. Core Launch focuses on the lead-to-quote-to-invoice foundation. Agreement tracking may be included in a relevant rollout where useful, but full e-signature workflow setup is usually a focused rollout or scoped setup.

Not necessarily. WindWeaver can support operational billing and accounting handoff, and it can often work alongside accounting tools. It does not replace professional accounting, tax, payroll, CPA, or legal advice.

The client owns their business data. Export details, provider limits, and legal terms are handled in the agreement instead of cluttering the sales pages.

WindWeaver is usually not the right fit for businesses that only need a basic website, want a completely self-serve app with no setup guidance, are unwilling to change any process, or need a large enterprise rollout immediately.