Diff

/var/www/vhosts/3dshawn.com/ptmatrix.3dshawn.com/TEMPLATES/tf_about.html

added on local at 2026-07-01 12:34:47

Added

+43

lines

Removed

-0

lines

Context

unchanged

Blobs

from
to 3bd71ffbc649

Restore this content →

Unified diff

Naive LCS-based line diff. Additions in emerald, deletions in rose. Both sides decompressed live from BLOB_STORE.

	1	<section class="hero" style="padding-bottom:30px">
	2	<div class="hero-inner">
	3	<h1>Built by builders for teams that ship.</h1>
	4	<p class="lead">PTMatrix exists because every PM tool we’ve tried either treats teams like individuals (no real org structure), treats individuals like rows in a database (no joy to use), or pretends customer tickets and project work are two different jobs (forcing every growing team to buy a second tool).</p>
	5	</div>
	6	</section>
	7
	8	<section class="section" style="max-width:760px">
	9	<h2>The wedge</h2>
	10	<div class="card mt-2">
	11	<p>Most growing teams stitch together 4–6 tools: Jira for engineering, Zendesk for customer support, Asana for the marketing team, Harvest for time, BambooHR for org structure, Zapier to glue it all together.</p>
	12	<p>Every one of those tools is good at one thing. The problem is that a customer bug report and an engineering sprint task are the <strong>same record</strong>, structured differently — and forcing them into two separate systems creates re-entry, double bookkeeping, and a gap where work gets lost between the cracks.</p>
	13	<p>PTMatrix folds the categories that <em>should</em> be one tool into one tool — project work, customer tickets, time tracking, the org chart, automations — and integrates with the rest of your stack instead of fighting it. The customer email, the bug ticket, and the engineering task are now the same row in the same database, with one assignee, one SLA, one comment thread.</p>
	14	</div>
	15	</section>
	16
	17	<section class="section" style="max-width:760px">
	18	<h2>What we believe</h2>
	19	<div class="card mt-2">
	20	<p><strong>1. Speed is a feature.</strong> If switching between Kanban and Gantt takes more than a click, we’ve lost. Every page in PTMatrix is engineered to load in under 200ms.</p>
	21	<p><strong>2. Departments are real.</strong> Most PM tools pretend the org is flat. We built PTMatrix for businesses where Engineering and Marketing report to different VPs, both touching the same project.</p>
	22	<p><strong>3. Reports exist to be acted on.</strong> Not a dashboard you check once. The right report tells you who to talk to today.</p>
	23	<p><strong>4. Tickets are tasks.</strong> A customer bug and a sprint task are the same row. Keeping them in separate systems creates re-entry, double bookkeeping, and a gap where work gets lost.</p>
	24	<p><strong>5. Your data is yours.</strong> No AI model training on your data, no resale to third parties, full export at any time, deletion within 30 days of cancel. The slip-cause AI feature uses your own Anthropic API key — we never see the prompts or responses.</p>
	25	</div>
	26	</section>
	27
	28	<section class="section" style="max-width:760px">
	29	<h2>What we don’t do</h2>
	30	<div class="card mt-2">
	31	<p>We’re honest about the gaps so you can make an informed decision.</p>
	32	<p><strong>We don’t do chat.</strong> Not native, not as a feature. Chat already exists at every customer (Slack / Teams / Webex / Discord), and PTMatrix has no business adding a fifth one. If you want ticket events in your team chat, use our generic outbound webhooks with Zapier or n8n.</p>
	33	<p><strong>We don’t do HR.</strong> The org chart is for routing work and finding the right person, not for PTO, comp reviews, or performance evaluations. BambooHR / Rippling / similar are great at that; we don’t want to compete poorly with them.</p>
	34	<p><strong>We don’t ship a self-service self-hosted distribution.</strong> Enterprise customers can request a custom deployment, but there is no Docker tarball you download and run. That is on the roadmap but not promised.</p>
	35	<p><strong>We’re not SOC 2 Type II yet.</strong> In progress; target Q4 2026. If you need that today, ask for our security questionnaire response and we’ll send the current state.</p>
	36	</div>
	37	</section>
	38
	39	<section class="section" style="text-align:center">
	40	<h2>Want in?</h2>
	41	<p class="section-lead">Start a 14-day free trial — or stay on the Free plan forever (3 users, unlimited projects).</p>
	42	<a href="/signup.cgi" class="btn btn-primary btn-xl">Start free trial →</a>
	43	</section>